[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #628 [TorBrowserButton]: Language cloaking doesn't hide character set
#628: Language cloaking doesn't hide character set
-------------------------------+-------------------------------------------
Reporter: sjmurdoch | Owner:
Type: defect | Status: new
Priority: major | Milestone: TorBrowserBundle 2.3.x-stable
Component: | Version:
TorBrowserButton | Keywords: tbb-fingerprinting, interview
Resolution: None | Parent ID:
Actual Points: |
Points: |
-------------------------------+-------------------------------------------
Comment (by dcf):
It seems that Accept-Charset was disabled in Firefox 10 (and IE 8, and
Safari 5, and Opera 11).
https://developer.mozilla.org/en-US/docs/HTTP/Content_negotiation
#The_Accept-Charset.3A_header:
> Considering that:
> * UTF-8 is now well-supported by all relevant user-agents,
> * the presence of the header increases the configuration-based entropy
exposed,
> * the presence of the header increases the data transmitted for each
request
> * almost no sites are using the value of this header for choosing
content during the negotiation,
> browsers started to stop sending this header in each request, starting
with Internet Explorer 8, Safari 5, Opera 11 and Firefox 10. In the
absence of Accept-Charset:, servers can simply assume that UTF-8 and the
most common characters sets are understood by the client.
[https://bugzilla.mozilla.org/show_bug.cgi?id=572652 Mozilla bug 572652],
"Remove the Accept-Charset header from HTTP requests," is VERIFIED FIXED.
http://wtfismyip.com/headers shows no Accept-Charset.
It appears to me that this bug is obsolete.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/628#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs