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 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.
Summary
application/x-www-form-urlencodedcontent type are properly encodedContext
The web app now allows GET request bodies in desktop mode. All content types (JSON, raw, multipart) were already handled correctly for GET, but form-urlencoded was explicitly skipped — causing the raw key-value pair array to be sent
instead of properly encoded
URLSearchParams.Changes
makeApiClientRequest.js: Changed!["GET", "HEAD"].includes(method)tomethod !== "HEAD"in the form-urlencoded body processing conditionTest plan
application/x-www-form-urlencodedbody → server should receive properly encoded form data (e.g.key1=value1&key2=value2)