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
Having problems since an update. #36
Comments
Wow, that is a crazy bug. I reported to to |
When switching to old version of body parser ~1.0.0 (1.0.2) which uses ~0.6.6 for qs, everything works as expected. |
Found that bug yesterday. Wanted to investigate a little bit more before reporting it. 👍 Try with this: |
I have made a PR ljharb/qs#13 to fix this. Just have to wait now :) |
Cool. As soon as there is a new qs I'll publish another patch version of this module with it. Sorry for any problems this caused :( there wasn't an easy way to get just the security fix without the using the qs rewrite, since the fix was only in 1.0.0. |
@dougwilson |
\m/ |
You guys work fast - thanks! |
Published as 1.6.2 |
I had this working before but now have updated to newer body parser in which I have tried both
and
with no success.
I've got the following form posting
with extended:false, looking at req.body I get:
or with extended: true
What I expect:
The text was updated successfully, but these errors were encountered: