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

urlencoded parser #61

Closed
talha-asad opened this issue Oct 22, 2014 · 1 comment
Closed

urlencoded parser #61

talha-asad opened this issue Oct 22, 2014 · 1 comment
Labels

Comments

@talha-asad
Copy link

I see that you have arrayLimit set to 100 which you pass onto qs module when the extended parser is being used, but this is not configurable by the end user, neither parameterLimit effects this. Can you expose this? This seems pretty trivial to me.

@dougwilson
Copy link
Contributor

For now, please refer to some old discussions on why this cannot be exposed: #55 (comment)

2.0 is on the horizon for this week, which will let you specify any parser and can essentially roll your own qs parser; in addition, if the 100 limit is hurting you, 99% of the time you should definitely not be using urlencoded bodies, but rather JSON.

dougwilson added a commit that referenced this issue Oct 30, 2014
closes #42
closes #43
closes #46
closes #58
closes #60
closes #61
closes #65
dougwilson added a commit that referenced this issue Nov 22, 2014
closes #42
closes #43
closes #46
closes #58
closes #60
closes #61
closes #65
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants