-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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(gatsby): fix issue with decoding URl #34816
Conversation
This comment was marked as spam.
This comment was marked as spam.
To make sure do we have tests around query-strings without escaping and paths without escaping. Just making sure that we didn't miss any use case |
@wardpeet We have quite a bit of e2e tests using regular query params. Some of them added for trailing slashes like gatsby/e2e-tests/production-runtime/cypress/integration/1-production.js Lines 211 to 222 in 1d3c331
So we should be set for baseline testing and would need just add cases for specifically encoded ones which for now was added for e2e/dev-runtime (we should add same ones to e2e/prod-runtime as well to be sure) |
We also have some here gatsby/e2e-tests/development-runtime/cypress/integration/navigation/redirect.js Lines 47 to 66 in 1d3c331
|
Thanks for the PR and the approval. Do push a release with the changes as we are eagerly waiting for this :). |
Hi @Abhirup-99, You can test this out in |
Description
Using a percent encoded character like
%25
in URL breaks due to multipledecodeURIComponent
calls. This PR address this issue by making sure the query string part of the URL is always encoded.Related Issues
Fixes #34797
Fixes #34998
[sc-46573]