Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: avoid serialization / deserialization of request body to query string and back #6333

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nickskalkin
Copy link
Contributor

paired with @dblandin on this one. This is not a final PR, just a proposal / conversation starter:

When working on #6331 we've noticed that when we send POST / PUT / DELETE requests with some data in them, the data is being converted (here, but it's not very obvious to understand) to query string params, and then back (here) before sending this data to the next service. Basically when we do gravityLoader('/something', { some: 'data' }), the data will be temporarily converted to /something?some=data. In most cases, this is not a problem.

But apparently it can be a problem sometimes, like, for example, with this issue mentioned above. @dblandin and I are wondering - should PPST / PUT / DELETE requests completely skip this weird intermediate step?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant