Prevent false positive in redirect_extraneous_paired_endpoint
which needlessly redirects (into infinity)
#6494
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
The
remove_query_arg()
function in WordPress is non-idempotent, meaning that if a query var is not present it can still result in a change to the URL (such as converting%20
to+
):This is problematic because
redirect_canonical()
does the opposite when it re-constructs the URL withparse_str()
andrawurlencode_deep()
, whererawurlencode_deep()
results in spaces being encoded as%20
instead of+
.The result is an infinite redirects between URLs with
+
and%20
when trying to access a URL with a query string that contains spaces in it.The fix is to check whether the URL explicitly has the query var before trying to remove it, rather than checking if the URL with the query var removed was changed. This is essentially the same thing that was done before in #5804.
Fixes #6492
Checklist