1804693 - Setting single proxy for all fails

Status: NEW

(Core :: Networking: Proxy, enhancement, P3)

Description

[erosman]

Attachment: firefox-settings2.png

In the old days, the proxy and PAC settings were protocol based.

• HTTP proxy -> HTTP target
• HTTPS proxy -> HTTPS target

The scheme PROXY in PAC also behaves that way. e.g.

By default, the PROXY keyword means that a proxy corresponding to the protocol of the original request, be it http, https, or ftp, is used.

However, above practice has been replaced in actual use for decades.

The practical use of proxy is often to use the the same proxy for all protocols which means:

• proxy:port -> HTTP/HTTPS/WS/WSS target

Currently, setting proxy:port as HTTP proxy and enabling httpProxyAll option, results in a connection to http://proxy:port

N.B. It might be that Firefox only regards port 443 as HTTPS (requires verification) which if the case, would also require updating.

Unless there is a method (direct via settings, or via API) to set an HTTPS proxy (other than 443 port), then the current proxy API fails contemporary requirements.

N.B. chrome.proxy singleProxy setting includes scheme to enforce required protocol. e.g.

In fact, the console screenshot is for a connection to an HTTPS site, but goes through HTTP proxy, which is unexpected.
Firefox -> Proxy (http://1.2.3.4:4443) -> https://example.com

Screenshots attached for reference.

Comment 1

[erosman]

Attachment: firefox-settings3.png

Comment 2

[BMO Automation]

Moving bug to Core/Networking: Proxy.

Comment 3

[Manuel Bucher [:manuel]]

fix whiteboard tag

Comment 4

[Manuel Bucher [:manuel]]

Added comment to wrong bug. Moved it to 1794464 comment 6