Privoxy HTTPS Proxy is not a Firefox HTTPS Proxy

[portiatrivisonno]

Privoxy and Firefox use the term "HTTPS Proxy" differently.

For Firefox under about:preferences --> Network Settings --> Settings the term "HTTPS Proxy" means the proxy which is being used for HTTPS connections (between browser and a web server), while a HTTP Proxy is used for HTTP connections.

In about:addons --> FoxyProxy --> Preferences --> Proxies --> Add --> Type the type "HTTPS" is not a Firefox HTTPS proxy. It seems its a proxy which is contacted using a TLS encrypted connection, i.e. the connection between browser and proxy is TLS encrypted.

Please adjust FoxyProxy's terminology to match Firefox's.
(It took me two days to figure this out)

[erosman]

One of the reasons FoxyProxy was created was to overcome Firefox's outdated native implementation. It is due to be changed.
Protocol-based proxying is no-longer suitable for the current situations which usually use a single server for all types of connections.

See also:

• Setting single proxy for all fails
• Proposal For Proxy Code and UI Enhancement

[portiatrivisonno]

It still would be nice to have an explanation what FoxyProxy understands under an "HTTPS" proxy or what "type" really means, e.g. in the help under "Individual Proxy"

[erosman]

Under proxy setting, the "Type" refers to the proxy-server's type. not the "destination" type.

Modern HTTPS proxy servers can handle both HTTP and HTTPS destination.
Similarly, modern HTTP proxy servers can handle both HTTP and HTTPS destination.

Firefox's outdated code assumed (and still assumes) that only HTTPS proxy servers can handle HTTPS destinations, and HTTP servers for HTTP destinations.

That was true in the very early days of HTTPS protocol introduction, but it changed not long after.

[portiatrivisonno]

Under proxy setting, the "Type" refers to the proxy-server's type. not the "destination" type.

Modern HTTPS proxy servers can handle both HTTP and HTTPS destination.
Similarly, modern HTTP proxy servers can handle both HTTP and HTTPS destination.

Exactly that. It would be nice if this would be documented in FoxyProxy instead of having this piece of information lurking in some random issues.

---

You don't have to convince me what terminology/approach is better (FWIW I see the merit of FoxyProxy's approach).
The core of the issue is that there are multiple meanings of "HTTPS proxy" in the same application (the browser) which confuses new users (e.g. me) and which they might stumble upon, e.g. they cannot convert their Firefox proxy config 1:1 to FoxyProxy and misconfigure FoxyProxy.

Thanks for your understanding and explanations.

[erosman]

Exactly that. It would be nice if this would be documented in FoxyProxy instead of having this piece of information lurking in some random issues.

I will see what can be done.
However, that is how proxies are. Chrome also handles the proxy the same way as FoxyProxy.
Only Firefox still uses the old method.
Therefore, the explanation only relates to Firefox (and should be part of Firefox's documentations) and not FoxyProxy (or Chrome).

[rodajc]

Privoxy and Firefox use the term "HTTPS Proxy" differently.

For Firefox under about:preferences --> Network Settings --> Settings the term "HTTPS Proxy" means the proxy which is being used for HTTPS connections (between browser and a web server), while a HTTP Proxy is used for HTTP connections.

In about:addons --> FoxyProxy --> Preferences --> Proxies --> Add --> Type the type "HTTPS" is not a Firefox HTTPS proxy. It seems its a proxy which is contacted using a TLS encrypted connection, i.e. the connection between browser and proxy is TLS encrypted.

Please adjust FoxyProxy's terminology to match Firefox's. (It took me two days to figure this out)

Did you manage to get FoxyProxy to work with Privoxy? If so, how?

[portiatrivisonno]

Did you manage to get FoxyProxy to work with Privoxy? If so, how?

Yes.

Assuming Privoxy is running on localhost port 8118, add a Proxy with the following values:

Field	Value	Note
Type	HTTP	not HTTPS
Hostname	127.0.0.1
Port	8118
Username		empty
Password		empty

[rodajc]

Yes. That works.
I thought I had tried all possibilities, but apparently I didn't.
Thanks a lot!