-
Notifications
You must be signed in to change notification settings - Fork 2k
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
If no content-type set in request w/ body, try parsing as 'application/json' first #192
Comments
This is fixed in Connect 2.x, so this will have to wait to get fixed until we upgrade Connect/Express. |
Closing in favor of: |
This was referenced Jul 9, 2020
This was referenced Aug 16, 2020
This was referenced Aug 27, 2020
This was referenced Sep 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a "problem" with Express-- but I believe assuming JSON is a fair choice given where things are going with application layer communications in today's apps.
More info on the current situation:
https://groups.google.com/forum/?fromgroups=#!topic/nodejs/_S8VSZzXEQA
Solution is overriding Express's bodyParser with a modified version which supports this functionality. Keep in mind we're on Express 2.x.
The text was updated successfully, but these errors were encountered: