How can Privoxy filter Secure (HTTPS) URLs?
1655 1656 Since secure HTTP connections are encrypted SSL sessions between your 1657 browser and the secure site, and are meant to be reliably secure, there is 1658 little that Privoxy can do but hand the raw gibberish data though from one 1659 end to the other unprocessed. 1660 1661 The only exception to this is blocking by host patterns, as the client 1662 needs to tell Privoxy the name of the remote server, so that Privoxy can 1663 establish the connection. If that name matches a host-only pattern, the 1664 connection will be blocked. 1665 1666 As far as ad blocking is concerned, this is less of a restriction than it 1667 may seem, since ad sources are often identifiable by the host name, and 1668 often the banners to be placed in an encrypted page come unencrypted 1669 nonetheless for efficiency reasons, which exposes them to the full power 1670 of Privoxy’s ad blocking. 1671 1672 “Content cookies” (those that are embedded in the actual HTML or JS page 1673 content, see filter{cont
