-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Remove X-Brave-Partner
from CORS safelist
#6041
Labels
custom headers
OS/Android
Fixes related to Android browser functionality
OS/Desktop
QA/No
release-notes/exclude
sec-low
Milestone
Comments
32 tasks
X-Brave-Partner
CORS request headerX-Brave-Partner
header and CORS safelist
32 tasks
kkuehlz
added a commit
to brave/brave-core
that referenced
this issue
Jun 13, 2020
navigator.brave.isBrave() can be used to identify brave. Resolves brave/brave-browser#6041
Also see #16455 for an interim step in the deprecation process. |
This is now gone; we should remove the unused constant: |
Thanks @bsclifton I will use this issue for the CORS cleanup. |
X-Brave-Partner
header and CORS safelistX-Brave-Partner
from CORS safelist
fmarier
added a commit
to brave/brave-core
that referenced
this issue
Mar 11, 2024
…ave/brave-browser#6041) This reverts commit 0ffd590. It should have been removed as part of 4cb8c2f.
24 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
custom headers
OS/Android
Fixes related to Android browser functionality
OS/Desktop
QA/No
release-notes/exclude
sec-low
Description
Initially added after Chromium 77 upgrade with brave/brave-core#3434
Per security review, this should be a temporary change.
A great time to do this would be when switching to our own user-agent for partners (see #1052)
The text was updated successfully, but these errors were encountered: