expose respectBeConservative as a property in browser.proxy.settings
Categories
(WebExtensions :: General, enhancement)
Tracking
(firefox72 fixed)
| Tracking | Status | |
|---|---|---|
| firefox72 | --- | fixed |
People
(Reporter: baku, Assigned: baku)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
This is another required pref for secure-proxy
|
Assignee | |
Comment 1•5 years ago
|
||
|
||
Comment 3•5 years ago
|
||
(In reply to Philipp Kewisch [:Fallen] [:📆] from comment #2)
Can you let me know what this does?
My suggested docstring for this: "If true (the default value), do not use newer TLS protocol features that might have interoperability problems on the Internet. This is intended only for use with critical infrastructure like the updates, and is only available to privileged addons."
Essentially, if a proxy locks in on tls 1.3, you need to disable this in order to proxy through that endpoint.
|
|
Assignee | |
Comment 4•5 years ago
|
||
Right. The pref network.http.proxy.respect-be-conservative has been introduced in bug 1585236 to avoid breaking firefox updates when secure-proxy (or any similar addon) is enabled.
|
||
Comment 6•5 years ago
|
||
| bugherder | ||
|
||
Comment 7•5 years ago
|
||
Hello,
Will this fix require manual validation? If yes, please provide some steps to reproduce in order to correctly test it and also, please set the "qe-verify+" flag. Otherwise, could the "qe-verify-" flag be added? Thanks!
|
|
Assignee | |
Updated•5 years ago
|
Description
•