Re: [whatwg/fetch] PATCH verb (#50)

This issue should be reopened.  I landed here because [this reddit thread](https://www.reddit.com/r/node/comments/i5u4m3/why_does_a_patch_request_only_work_when_the/) shows more developers are getting tripped up by this.

> As I mentioned, we'd break projects that are using HTTP correctly and want to use patcH for some reason.

@annevk In your own words, "Do you have some data to back that up?"  I.e. Do you have any examples of projects that rely on such a distinction?  I'd be genuinely surprised if such exist.  The vast majority of developers expect HTTP methods to be uppercase or case-independent.  For those few that are aware of the distinction, relying on the fact "patch" is the one standard method that's case-sensitive would seem extremely ill-advised. Any code leveraging this quirky behavior would have to be considered an inelegant hack, at best (imho).

I'm with the other commenters here - I don't understand the current rationalization for maintaining this.   Yes, the HTTP spec says methods are case-sensitive, but the Fetch authors have clearly decided to ignore that by normalizing the standard HTTP methods.  Leaving "patch" as the odd one out makes no sense.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/50#issuecomment-670928396