This repository was archived by the owner on Feb 27, 2022. It is now read-only.
Fixed handling of parameters with names that are keys in Object.prototype. #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the current code, if a query string parameter has a name with a key in Object.prototype, then the query string parse logic will treat the existing value as if it had been passed first in the query string.
Example:
Expected behavior: 'toString=bar' => { toString: 'bar' }
Actual behavior: 'toString=bar' => { toString: [Object.prototype.toString, 'bar'] }
This commit changes the existing parameter check to use Object.prototype.hasOwnProperty, which prevents influence from Object.prototype's keys.