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

Allow = character in parameter value #408

Merged
merged 6 commits into from
Jan 25, 2021
Merged

Conversation

joheredi
Copy link
Member

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

@xirzec
Copy link
Member

xirzec commented Jan 21, 2021

I'm ok with this change, since it maps to the platform URL parsing behavior

Copy link
Contributor

@daviwil daviwil left a 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!

@ramya-rao-a
Copy link
Contributor

Do we have the same problem in @azure/core-http?

@joheredi
Copy link
Member Author

Do we have the same problem in @azure/core-http?

I just checked and this is not an issue in core-http

@joheredi
Copy link
Member Author

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

@joheredi joheredi merged commit 7ca0e99 into Azure:master Jan 25, 2021
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

Successfully merging this pull request may close these issues.

URLQuery.parse fails parsing when = sign in parameter value
4 participants