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

If no content-type set in request w/ body, try parsing as 'application/json' first #192

Closed
mikermcneil opened this issue Mar 2, 2013 · 2 comments · May be fixed by rx007/sails#2
Closed

Comments

@mikermcneil
Copy link
Member

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.

@mikermcneil
Copy link
Member Author

This is fixed in Connect 2.x, so this will have to wait to get fixed until we upgrade Connect/Express.

@mikermcneil
Copy link
Member Author

Closing in favor of:
#51

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

Successfully merging a pull request may close this issue.

1 participant