fix proxy call content-length header for encoded characters in payload #1974
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.
Closes: #1968
Description
The backend passthrough proxy used string length for the
content-length
header which does not match the byte length of a payload which contains encoded characters. Therefore the payload was cut short when received by the api server resulting in malformed JSON being received.How Has This Been Tested?
Any request that uses our pass through proxy can be used for testing.
Easiest to test with projects.
Create a new project named
testł
.Expect the project to be created successfully.
Test Impact
No backend tests.
Request review criteria:
Self checklist (all need to be checked):
If you have UI changes:
After the PR is posted & before it merges:
main