-
-
Notifications
You must be signed in to change notification settings - Fork 454
qs.parse is parsing the string with + properly #305
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
Comments
https://stackoverflow.com/questions/2678551/when-to-encode-space-to-plus-or-20 |
@sindresorhus Not working |
This is the behavior of the browser API too:
And this is how it should have looked like if it had been properly encoded:
|
In such cases, I think using Base64 is much safer than passing it as a raw string. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
?externaluserid=454545454&email=abc+123@gmail.com&order=165615&token=dtc5uwvmkC
is converting the email's + to a space.
{email: "abc 123@gmail.com", externaluserid: "454545454", token: "dtc5uwvmkC", order: "165615"}
It should keep + in email instead of converting this to a space.
The text was updated successfully, but these errors were encountered: