fix: open redirect_to URL in browser to prevent infinite deep link loop#22665
Merged
fix: open redirect_to URL in browser to prevent infinite deep link loop#22665
Conversation
…op (#22648) * fix: open redirect_to URL in browser to prevent infinite deep link loop When a tracking URL's redirect_to target can't be handled in-app, open the extracted redirect_to URL in the browser instead of the original tracking URL. This prevents an infinite loop caused by the app's intent filter re-intercepting its own public-api.wordpress.com/bar/ URLs. * fix: fire server tracking pixel when redirect_to opens in browser When a tracking URL's redirect_to target can't be handled in-app, the app now opens the redirect destination in the browser (loop fix) but the server never sees the original tracking URL. Fire the pixel explicitly in this path so email link taps are still recorded. The no-redirect fallback still opens /bar/ in the browser, which handles tracking implicitly via the browser's HTTP request.
|
Contributor
|
|
Contributor
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## trunk #22665 +/- ##
=======================================
Coverage 38.01% 38.01%
=======================================
Files 2268 2268
Lines 116715 116720 +5
Branches 16178 16180 +2
=======================================
+ Hits 44371 44376 +5
Misses 68707 68707
Partials 3637 3637 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
dcalhoun
approved these changes
Mar 9, 2026
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
3 participants
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.
This PR merges the #22648 changes in the release/26.6.1 branch to the trunk branch.
When a tracking URL's redirect_to target can't be handled in-app, open the extracted redirect_to URL in the browser instead of the original tracking URL. This prevents an infinite loop caused by the app's intent filter re-intercepting its own public-api.wordpress.com/bar/ URLs.
When a tracking URL's redirect_to target can't be handled in-app, the app now opens the redirect destination in the browser (loop fix) but the server never sees the original tracking URL. Fire the pixel explicitly in this path so email link taps are still recorded.
The no-redirect fallback still opens /bar/ in the browser, which handles tracking implicitly via the browser's HTTP request.
Description
Testing instructions