-
Notifications
You must be signed in to change notification settings - Fork 983
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
body parser doesn't treat content types as case-insensitive #877
Comments
Thanks for finding this bug. Do you have the cycles to send a PR? |
gcochard
added a commit
to gcochard/node-restify
that referenced
this issue
Aug 14, 2015
yunong
added a commit
that referenced
this issue
Aug 14, 2015
Fixed. |
fixed as part of 395c042 |
👍 great work guys! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Example server:
When called as follows,
req.body
unexpectedly is aBuffer
:(notice the content type case)
It works as expected with this:
According to RFC2045: "Matching of media type and subtype is ALWAYS case-insensitive".
The text was updated successfully, but these errors were encountered: