Closed
Bug 1827635
Opened 2 years ago
Closed 2 years ago
Sync up RFP's Spoofed HTTP Header with network.http.useragent.forceRVOnly
Categories
(Core :: Networking: HTTP, defect, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
DUPLICATE
of bug 1818889
People
(Reporter: tjr, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: [necko-triaged])
network.http.useragent.forceRVOnly is set to 109 by default, which makes RFP's Spoofed User Agent header distinguishable from a regular Firefox header.
While this is hardly the only thing that makes RFP distinguishable, it's still worth fixing, especially since user agent gets logged all over.
Comment 1•2 years ago
•
|
||
see Bug 1818889 which we want to apply to all platforms (not just desktop), see https://bugzilla.mozilla.org/show_bug.cgi?id=1818889#c2
tor ticket: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41652
it's still worth fixing, especially since
also compat
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P2
Updated•2 years ago
|
Whiteboard: [necko-triaged]
Comment 2•2 years ago
|
||
I believe this bug is a duplicate of bug 1818889. I have a patch for bug 1818889 to add RFP support for the network.http.useragent.forceRVOnly
pref.
You need to log in
before you can comment on or make changes to this bug.
Description
•