Remove the "network.http.useragent.forceVersion" pref
Categories
(Core :: Networking: HTTP, task, P3)
Tracking
()
People
(Reporter: cpeterson, Assigned: cpeterson)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
When Firefox hit version 100 (2022-03-08), some websites broke when parsing the three-digit version number. We could use Firefox’s site interventions to send a version 99 UA string to those sites, but we can’t override the UA for enterprise intranet sites we don't know about. So the "network.http.useragent.forceVersion" pref was added (in bug 1753805) to allow enterprise admins to force a version 99 UA string if needed.
Now that the Firefox 100 release is 14 months behind us and the next ESR (version 115) is riding the trains, we can confidently remove the pref. Enterprise admins using ESR will have another year of using the pref in ESR 115. Then they'll need to fix their intranet sites to work with Firefox 100+.
|
Assignee | |
Comment 1•2 years ago
|
||
When Firefox hit version 100 (2022-03-08), some websites broke when parsing the three-digit version number. We could use Firefox’s site interventions to send a version 99 UA string to those sites, but we can’t override the UA for enterprise intranet sites we don't know about. So the "network.http.useragent.forceVersion" pref was added (in bug 1753805) to allow enterprise admins to force a version 99 UA string if needed.
Now that the Firefox 100 release is 14 months behind us and the next ESR (version 115) is riding the trains, we can confidently remove the pref. Enterprise admins using ESR will have another year of using the pref in ESR 115. Then they'll need to fix their intranet sites to work with Firefox 100+.
|
||
Comment 2•2 years ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: As a heads-up to admins to fix their websites before the next ESR.
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
Description
•