Skip to content
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

Closed
bsclifton opened this issue Sep 16, 2019 · 3 comments · Fixed by brave/brave-core#22539
Closed

Remove X-Brave-Partner from CORS safelist #6041

bsclifton opened this issue Sep 16, 2019 · 3 comments · Fixed by brave/brave-core#22539
Assignees

Comments

@bsclifton
Copy link
Member

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)

@bridiver bridiver changed the title Remove safelisting for X-Brave-Partner CORS request header Remove X-Brave-Partner header and CORS safelist Jun 12, 2020
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
@fmarier
Copy link
Member

fmarier commented Jun 16, 2021

Also see #16455 for an interim step in the deprecation process.

@bsclifton
Copy link
Member Author

@fmarier
Copy link
Member

fmarier commented Mar 11, 2024

Thanks @bsclifton I will use this issue for the CORS cleanup.

@fmarier fmarier reopened this Mar 11, 2024
@fmarier fmarier self-assigned this Mar 11, 2024
@fmarier fmarier changed the title Remove X-Brave-Partner header and CORS safelist Remove X-Brave-Partner from CORS safelist Mar 11, 2024
fmarier added a commit to brave/brave-core that referenced this issue Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment