PATCH HTTP method normalization about fetch

[annevk]

Support does not mean it needs normalization though.

[h2non]

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]

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]

Agreed! Thank you

[annevk]

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