You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, HTTP Methods in 1.1 are all uppercase. The preference for 2.0 so far appears to have those represented using all lowercase. The HTTP Mapping currently does not redefine the HTTP Method header to use lowercase values. Need to clarify whether or not HTTP methods in 2.0 are case sensitive or not.
The text was updated successfully, but these errors were encountered:
My understanding is that the name of the method header is lowercase, i.e. ":method"
But the value of the header is the normal HTTP/1.1 case-sensitive method defined in RFC-2616/Sec-5.1.1
Look at the header compression draft for an example.. the pre-filled request table shows "get" and not "GET". I've seen lower case used in a few other areas as well. It just needs to be clarified.
We can't re-define the range of HTTP methods without changing the semantics of HTTP. So, I'm marking this as editorial (to correct/clarify as necessary).
Currently, HTTP Methods in 1.1 are all uppercase. The preference for 2.0 so far appears to have those represented using all lowercase. The HTTP Mapping currently does not redefine the HTTP Method header to use lowercase values. Need to clarify whether or not HTTP methods in 2.0 are case sensitive or not.
The text was updated successfully, but these errors were encountered: