Make FPCentral recognize Tor Browser 7.0 and show "acceptable values"

FPCentral is recognizing the browser based on its user agent, and shows the "acceptable value" for each attribute.

It currently recognize Tor Browser 6.5. We should make it recognize Tor Browser 7.0.

added TorBrowserTeam201706 component::applications/quality assurance and testing owner::boklm parent::6119 priority::medium resolution::fixed severity::normal status::closed type::task labels

This is done in this patch: https://github.com/plaperdr/fp-central/pull/7

The PR has been accepted and deployed on the server. For the Accept-Encoding header, which value is the right one: "gzip, deflate, br" or "gzip, deflate" ?

Trac:
Username: Octopus

Thanks. Closing this ticket.

Trac:
Status: new to closed
Resolution: N/A to fixed

What was the answer on the question in comment:2? :)

Replying to Octopus:

For the Accept-Encoding header, which value is the right one: "gzip, deflate, br" or "gzip, deflate" ?

Hmm, on my instance of fpcentral, I get "gzip, deflate", but on https://fpcentral.irisa.fr/fp I get "gzip, deflate, br".

I'm not sure why. Maybe this depends on how the web server was deployed?

Replying to boklm:

Replying to Octopus:

For the Accept-Encoding header, which value is the right one: "gzip, deflate, br" or "gzip, deflate" ?

Hmm, on my instance of fpcentral, I get "gzip, deflate", but on https://fpcentral.irisa.fr/fp I get "gzip, deflate, br".

I'm not sure why. Maybe this depends on how the web server was deployed?

There are two preferences: network.http.accept-encoding and network.http.accept-encoding.secure which have gzip, deflate and gzip, deflate, br as respective values. So, it seems the answer is "it depends".

Ah, so it depends whether we access it through http or https.

closed

moved to tpo/applications/tor-browser-bundle-testsuite#22656 (closed)