Authorized H2 proxies break with HTTPS
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: yegors, Unassigned)
Details
Attachments
(1 file)
|
3.29 MB,
video/mp4
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36
Steps to reproduce:
- Load a proxy into the browser using the proxy API
- Register an onAuthRequired listener to supply the authentication when prompted
- Load any HTTPS website
Actual results:
Browser shows "The proxy server is refusing connections" error for all HTTPS requests.
If you then make an insecure HTTP request, the request gets proxied correctly. Then, HTTPS requests start working too.
Expected results:
The first HTTPS request should have triggered the onAuthRequired listener, supplied the correct credentials and completed the request.
This only occurs if you're using SPDY/H2 secure proxies. Cannot reproduce with http/1.1 proxies.
Could be related to https://bugzilla.mozilla.org/show_bug.cgi?id=1561665 which is fixed in FF69 beta, but the above mentioned issue still persists.
In our extension we're forced to make a HTTP request every time we switch the proxy in the browser to "clear the plumbing" so to speak, but this is hacky and also does not work in private windows since the extension makes the request in a "standard" window, which is isolated from the private window. See the attached video.
I should add that neither of these things are an issue in Chrome, everything works as expected.
|
||
Comment 2•5 years ago
|
||
Hi Yegors,
I was not able to reproduce it.
I'll add a product and component to this ticket so the devs can take a look at it.
In the meantime, can you please download the latest Firefox Nightly version and try printing a document with both printers? Let us know your input. You can download Nightly from here: https://nightly.mozilla.org/.
Both printers? I think you got a wrong issue.
|
|
||
Comment 4•5 years ago
|
||
Hi Yegors,
I apologize for my mistake. For this case and due to I was not able to reproduce it, could you please try to retest this on the latest Nightly version and tell us if the error still happen?.
|
||
Updated•5 years ago
|
Issue not resolved in the latest Nightly.
Description
•