Created by: sebastien-rosset
Fix problem with HTTP signatures when the URL path and/or query include characters that need to be encoded. For example, /api/v1/Request?$orderby=-CreateTime&$top=10 may be encoded to /api/v1/Request?%24orderby=-CreateTime&%24top=10 on the wire. When the HTTP signature includes the (request-target) field, the path and query must be written exactly as it is on the wire.
PR checklist
-
Read the contribution guidelines. -
If contributing template-only or documentation-only changes which will change sample output, build the project beforehand. -
Run the shell script ./bin/generate-samples.shto update all Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./bin/generate-samples.sh bin/config/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.