According to Privoxy documentation
4.15. How can Privoxy filter Secure (HTTPS) URLs?
Since secure HTTP connections are encrypted SSL sessions between your browser and the secure site, and are meant to be reliably secure, there is little that Privoxy can do but hand the raw gibberish data though from one end to the other unprocessed.
The only exception to this is blocking by host patterns, as the client needs to tell Privoxy the name of the remote server, so that Privoxy can establish the connection. If that name matches a host-only pattern, the connection will be blocked.
blocking by host pattern should work independently of the protocol used (HTTP or HTTPS)
For instance:
{ +block{Nasty ads.} }
.somesite.com/imp
effectively blocks http://test.somesite/imp
but not https://test.somesite/imp
The browsers I use are configured to use Privoxy proxy for both HTTP and HTTPS.
Is it a bug or an expected behavior, in spite of what the doc says? (I'm using v3.0.26)