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.

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

HTTP Method Case #164

Closed
jasnell opened this issue Jul 3, 2013 · 4 comments
Closed

HTTP Method Case #164

jasnell opened this issue Jul 3, 2013 · 4 comments

Comments

@jasnell
Copy link
Contributor

jasnell commented Jul 3, 2013

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.

@jpinner
Copy link

jpinner commented Jul 3, 2013

Where is this preference?

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

@jasnell
Copy link
Contributor Author

jasnell commented Jul 3, 2013

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.

@mnot
Copy link
Member

mnot commented Jul 3, 2013

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).

@martinthomson
Copy link
Collaborator

I don't believe this to be necessary. I've changed the examples to include uppercase methods, which seems to be adequate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants