Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PATCH HTTP method normalization #17

Closed
h2non opened this issue Nov 21, 2014 · 5 comments
Closed

PATCH HTTP method normalization #17

h2non opened this issue Nov 21, 2014 · 5 comments

Comments

@h2non
Copy link

h2non commented Nov 21, 2014

It could be added since XHR2 support PATCH method
https://fetch.spec.whatwg.org/#methods
@annevk
Copy link
Member

annevk commented Nov 22, 2014

Support does not mean it needs normalization though.

@h2non
Copy link
Author

h2non commented Nov 22, 2014

Which kind of criteria you are using to determine it cannot should be normalized?
According to the RFC, it's treated with the same conditions as another HTTP verb (like a young child of the PUT method), with emphasis on partial resource modifications

It's in fact a misunderstood method, but it will be more used since people could know it better, like reading it in further specifications

@annevk
Copy link
Member

annevk commented Nov 22, 2014

The criteria is whether we have to uppercase it for legacy compatibility. Method names are case-sensitive in theory and I'd rather not prevent more legitimate method names, such as patch and pAtCh.

@h2non
Copy link
Author

h2non commented Nov 22, 2014

Agreed! Thank you

@h2non h2non closed this as completed Nov 22, 2014
annevk added a commit that referenced this issue Nov 23, 2014
@annevk
Explain method normalization for #17
8e188e9
@annevk
Copy link
Member

annevk commented Nov 23, 2014

I decided to explain this in the standard since it was not particularly clear, so thank you too!

@dgraham dgraham mentioned this issue Jan 21, 2015
Closed
yutakahirano added a commit that referenced this issue Jun 23, 2020
@yutakahirano
# This is a combination of 2 commits.
db9fbcd 
# This is the 1st commit message:

# This is a combination of 23 commits.
# This is the 1st commit message:

Integrate CORP and COEP

This is part of the introduction of COEP
(whatwg/html#5454). The CORP check now takes
COEP into account. Also, responses coming from service workers
are checked.

# This is the commit message #2:

Update fetch.bs

Co-authored-by: Domenic Denicola <[email protected]>
# This is the commit message #3:

Update fetch.bs

Co-authored-by: Domenic Denicola <[email protected]>
# This is the commit message #4:

fix

# This is the commit message #5:

fix

# This is the commit message #6:

fix

# This is the commit message #7:

fix

# This is the commit message #8:

fix

# This is the commit message #9:

fix

# This is the commit message #10:

fix

# This is the commit message #11:

fix

# This is the commit message #12:

fix

# This is the commit message #13:

fix

# This is the commit message #14:

fix

# This is the commit message #15:

fix

# This is the commit message #16:

fix

# This is the commit message #17:

fix

# This is the commit message #18:

Update fetch.bs

Co-authored-by: Anne van Kesteren <[email protected]>
# This is the commit message #19:

Update fetch.bs

Co-authored-by: Anne van Kesteren <[email protected]>
# This is the commit message #20:

fix

# This is the commit message #21:

fix

# This is the commit message #22:

fix

# This is the commit message #23:

fix

# This is the commit message #2:

fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@h2non @annevk