Modified query parameter encoding to not percent-encode characters allowed in query strings per RFC3986 #124
Conversation
This file contains 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
…lowed in query strings per RFC3986 Signed-off-by: Mike Raineri <michael.raineri@dell.com>
…erly without percent-encoding Signed-off-by: Mike Raineri <michael.raineri@dell.com>
mraineri
force-pushed
the
Query-Encoding
branch
from
e14ebb8
to
b668996
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
From the RFC, the query string follows this definition:
*( pchar / "/" / "?" )pchar is defined as:
unreserved / pct-encoded / sub-delims / ":" / "@"unreserved is defined as:
ALPHA / DIGIT / "-" / "." / "_" / "~"sub-delims is defined as
"!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "="So, characters like $ (and others used in Redfish) do not need to be percent-encoded per the RFC.