-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Farbled HTTP Accept-Language header does not have a q value #24126
Comments
The above requires |
Verification PASSED on
Verified test plan from brave/brave-core#14235 (comment). See this comment for note re: Went through the STR/Cases outlined via brave/brave-core#14235 (comment) and ensured that all the cases via https://dev-pages.brave.software/fingerprinting/headers.html were working as per the following: Before running through the cases, ensured that
Went through the following once
|
Example |
Example |
Example |
---|---|---|
Kannada
Example |
Example |
Example |
---|---|---|
Language FP
enabled & Allow fingerprinting
(Disabled)
English
- ensured that the value under
Headers
displays all the languages listed viabrave://settings/languages
Example |
Example |
Example |
---|---|---|
Hindi
- ensured that the value under
Headers
displays all the languages listed viabrave://settings/languages
Example |
Example |
Example |
---|---|---|
Language FP
enabled & Aggressively block fingerprinting
(Aggressive)
- ensured that the value under
Headers
always displaysen
despite the languages listed underbrave://settings/languages
Example |
Example |
Example |
---|---|---|
Also went through the following cases once Prevent sites from fingerprinting me based on my language preferences
was disabled via brave://settings/shields
Language FP
disabled & Block fingerprinting
(Default)
- ensured that all the languages are being displayed via the
Header
asAccept-Language
has been disabled
Example |
Example` |
---|---|
Language FP
disabled & Allow fingerprinting
(Disabled)
- ensured that all the languages are being displayed via the
Header
asAccept-Language
has been disabled
Example |
Example` |
---|---|
Language FP
disabled & Aggressively block fingerprinting
(Aggressive)
Verified with
Verified test plan from brave/brave-core#14235 (comment). See this comment for note re: Went through the STR/Cases outlined via brave/brave-core#14235 (comment) and ensured that all the cases via https://dev-pages.brave.software/fingerprinting/headers.html were working as per the following: Before running through the cases, ensured that
Went through the following once
|
Example |
Example |
Example |
---|---|---|
French
Example |
Example |
Example |
---|---|---|
Language FP
enabled & Allow fingerprinting
(Disabled)
- ensured that the value under
Headers
displays all the languages listed viabrave://settings/languages
Example |
Example |
Example |
---|---|---|
Language FP
enabled & Aggressively block fingerprinting
(Aggressive)
- ensured that the value under
Headers
always displaysen
despite the languages listed underbrave://settings/languages
Example |
Example |
Example |
---|---|---|
Also went through the following cases once Prevent sites from fingerprinting me based on my language preferences
was manually disabled via brave://settings/shields
:
Language FP
disabled & Block fingerprinting
(Default)
- ensured that all the languages are being displayed via the
Header
asAccept-Language
has been disabled
Example |
Example` |
---|---|
Language FP
disabled & Allow fingerprinting
(Disabled)
- ensured that all the languages are being displayed via the
Header
asAccept-Language
has been disabled
Example |
Example` |
---|---|
Language FP
disabled & Aggressively block fingerprinting
(Aggressive)
Verification
Refered to Testing Plan in brave/brave-core#14235 (comment) Quick Note: As per @pes10k, both of the Navigation and Sub-resource columns don't match which is a bug and expected. This will be fixed in a follow up issue via brave/brave-core#14338 as per @pes10k. Went through the STR/Cases outlined via brave/brave-core#14235 (comment) and ensured that all the cases via https://dev-pages.brave.software/fingerprinting/headers.html were working as per the following: brave://version Language FP enabled & Block fingerprinting (Default) ensured that the value under Headers matches the first language set via brave://settings/languages
Language FP enabled & Allow fingerprint (Disabled) ensured that the value under Headers displays all the languages listed via brave://settings/languages
Language FP enabled & Block fingerprinting (Aggressive) ensured that the value under Headers always displays en despite the languages listed under brave://settings/languages
Because Android doesn't have the Prevent sites from fingerprinting me based on my language preferences toggle implemented like desktop, went through the below after disabling brave://flags#brave-reduce-language. Language FP disabled & Block fingerprinting (Default) ensured that all the languages are being displayed via the Header as Accept-Language has been disabled
Language FP disabled & Allow fingerprint (Disabled) ensured that all the languages are being displayed via the Header as Accept-Language has been disabled
Language FP disabled & Block fingerprinting (Aggressive) |
Verification
Refered to Testing Plan in brave/brave-core#14235 (comment) Went through the STR/Cases outlined via brave/brave-core#14235 (comment) and ensured that all the cases via https://dev-pages.brave.software/fingerprinting/headers.html were working as per the following: brave://version Language FP enabled & Block fingerprinting (Default) ensured that the value under Headers matches the first language set via brave://settings/languages
Language FP enabled & Allow fingerprint (Disabled) ensured that the value under Headers displays all the languages listed via brave://settings/languages
Language FP enabled & Block fingerprinting (Aggressive) ensured that the value under Headers always displays en despite the languages listed under brave://settings/languages
Because Android doesn't have the Prevent sites from fingerprinting me based on my language preferences toggle implemented like desktop, went through the below after disabling brave://flags#brave-reduce-language. Language FP disabled & Block fingerprinting (Default) ensured that all the languages are being displayed via the Header as Accept-Language has been disabled
Language FP disabled & Allow fingerprint (Disabled) ensured that all the languages are being displayed via the Header as Accept-Language has been disabled
Language FP disabled & Block fingerprinting (Aggressive) |
Verified with
Verified test plan from brave/brave-core#14235 (comment). See this comment for note re: Went through the STR/Cases outlined via brave/brave-core#14235 (comment) and ensured that all the cases via https://dev-pages.brave.software/fingerprinting/headers.html were working as per the following: Before running through the cases, ensured that
Went through the following once
|
Example |
Example |
Example |
---|---|---|
Spanish
Example |
Example |
Example |
---|---|---|
Language FP
enabled & Allow fingerprinting
(Disabled)
- ensured that the value under
Headers
displays all the languages listed viabrave://settings/languages
Example |
Example |
Example |
---|---|---|
Language FP
enabled & Aggressively block fingerprinting
(Aggressive)
- ensured that the value under
Headers
always displaysen
despite the languages listed underbrave://settings/languages
Example |
Example |
Example |
---|---|---|
Also went through the following cases once Prevent sites from fingerprinting me based on my language preferences
was manually disabled via brave://settings/shields
:
Language FP
disabled & Block fingerprinting
(Default)
- ensured that all the languages are being displayed via the
Header
asAccept-Language
has been disabled
Example |
Example` |
---|---|
Language FP
disabled & Allow fingerprinting
(Disabled)
- ensured that all the languages are being displayed via the
Header
asAccept-Language
has been disabled
Example |
Example` |
---|---|
The initial design of Accept-Language farbling specified that, in aggressive anti-fingerprinting mode, the value should always be "en-US,en". However, webcompat testing has since revealed that some frameworks react poorly to the lack of a q value.
Suggest we change the aggressive value to "en-US,en;q=0.9" which matches a Chromium's default behavior for en-US users.
The text was updated successfully, but these errors were encountered: