-
Notifications
You must be signed in to change notification settings - Fork 55
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
Allow = character in parameter value #408
Conversation
I'm ok with this change, since it maps to the platform URL parsing behavior |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it works fine in Node and the browser, I don't see any reason not to use it!
Do we have the same problem in |
17a6451
to
4bf3c51
Compare
4bf3c51
to
d8215db
Compare
I just checked and this is not an issue in core-http |
Merging, the only non-passing test is the check-everything. I'm not updating the package version in favor of #410 which is updating the version and we want both fixes to be part of the same release |
Currently, ms-rest-js marks a query parameter as invalid and drops it if it contains an
=
character.According to RFC 3896 "reserved" characters should be encoded (link). However, nodejs and browser's native URL seems to handle = in the parameter value just fine.
With this PR ms-rest-js parsing will allow
=
in a query parameter value.Fixes #406