Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Fungovanie tejto stránky je z dôvodu údržby dočasne obmedzené. Ak článok nevyrieši váš problém a chcete položiť otázku, napíšte našej komunite podpory na Twitter @FirefoxSupport alebo Reddit /r/firefox.

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

Accept-language header in private mode

more options

Is there any setting to stop accept-language header request, or change it to default in Private mode, with tracking protection enabled.

from https://w3ctag.github.io/private-mode/ drafts Browsers in private mode MUST NOT emit any of the following request header fields: Accept, Accept-Language ...

Is there any setting to stop accept-language header request, or change it to default in Private mode, with tracking protection enabled. from https://w3ctag.github.io/private-mode/ drafts Browsers in private mode MUST NOT emit any of the following request header fields: Accept, Accept-Language ...

Všetky odpovede (1)

more options

Whose draft is that? It seems rather extreme, but I guess that would be a comment for the discussion thread: https://github.com/w3ctag/design-reviews/issues/101

I notice the stated purpose of that section of restrictions is:

Maintaining server privacy means limiting its ability to identify the user, through "fingerprinting" the client, or associating the user's behavior on one site with that on another (using a mechanism like cookies).

I'm not aware of any preferences that modulate the HTTP headers sent in private mode. There may be extensions that can do that.

There is a preference in testing called privacy.resistFingerprinting which may have some of those effects. However, users have reported some website breakage with that setting, so it probably needs further development. It is expected to be "turned on" in Firefox 59.

More info: https://wiki.mozilla.org/Security/Fingerprinting