Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

urlencoded strings not handled properly #43

Closed
qzaidi opened this Issue Sep 17, 2012 · 2 comments

Comments

Projects
None yet
2 participants

qzaidi commented Sep 17, 2012

I am submitting a form where the '=' character is present, although its urlencoded.

querystring fails to handle this, but node's builitin querystring module handles it just fine.

qs.parse('tBK0FKOvgZw%3D=Uu%2BujGnmB1Y%3D')

should return

{ 'tBK0FKOvgZw=': 'Uu+ujGnmB1Y=' } (and this is what the builtin module returns)

but it gives this instead

{ 'tBK0FKOvgZw': '=Uu+ujGnmB1Y=' }

Owner

tj commented Sep 18, 2012

we must be doing an indexOf after decoding, I'll look

@tj tj closed this in 9d829d3 Sep 18, 2012

qzaidi commented Sep 19, 2012

Yes, it url decodes first and then takes the first equality sign it finds.

On 9/19/12, TJ Holowaychuk notifications@github.com wrote:

we must be doing an indexOf after decoding, I'll look


Reply to this email directly or view it on GitHub:
visionmedia#43 (comment)

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