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

Decoding in parse() applied too late #272

Open
Mereidos opened this issue Aug 5, 2020 · 0 comments
Open

Decoding in parse() applied too late #272

Mereidos opened this issue Aug 5, 2020 · 0 comments

Comments

@Mereidos
Copy link

Mereidos commented Aug 5, 2020

The decoding that takes place in parse() happens too late, leading to encoded '?', '&' and '=' signs not being interpreted correctly:

VERSION:
6.13.1

ACTUAL RESULT:
parse(?key1=value1&key2=value2) returns: {"key1":"value1","key2":"value2"}
parse(%3Fkey1%3Dvalue1%26key2%3Dvalue2) returns: {"?key1=value1&key2=value2":null}

EXPECTED RESULT:
parse(?key1=value1&key2=value2) returns: {"key1":"value1","key2":"value2"}
parse(%3Fkey1%3Dvalue1%26key2%3Dvalue2) returns: {"key1":"value1","key2":"value2"}

@Mereidos Mereidos changed the title Decoding in parse applied too late Decoding in parse() applied too late Aug 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant