-
Notifications
You must be signed in to change notification settings - Fork 2.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
Strip referer to strict-origin-when-cross-origin in all cases #13464
Comments
To solve webcompat problems we replace forcing "no-referrer" for cross-site top-level navigations with capping with "strict-origin-when-cross-origin". Fix brave/brave-browser#13464
Moving into
|
Waiting on new
|
Verification passed on
Verification passed on
Verified the test plan from brave/brave-core#7591 Verified passed with
Verified the test plan from brave/brave-core#7591 Confirmed tests from the following pages worked as expected:
Verification passed on Brave v1.19.86 on Samsung Galaxy Tab S5e (Android 9.0) Verified the test plan from brave/brave-core#7591 Confirmed tests from the following pages worked as expected:
Verification PASSED on
|
This is a follow up to #13434 (which is no longer needed)
Brave currently completely strips the referrer on all cross origin top-frame navigations. This causes Brave to look like bots / fraud for some non-malicious systems (e.g., DDG and similar).
We should change Brave's referrer policy to cap at (i.e. send less when the page requests less, but cap and default to
strict-origin-when-cross-origin
)The text was updated successfully, but these errors were encountered: