On some HTTPS sites my browser warns me about unauthenticated content, the URL bar doesn get highlighted and the lock symbol appears to be broken. Whats going on?
Probably the browser is requesting ads through HTTPS and Privoxy is blocking the requests. Privoxy’s error messages are delivered unencrypted and while it’s obvious for the browser that the HTTPS request is already blocked by the proxy, some warn about unauthenticated content anyway. To work around the problem you can redirect those requests to an invalid local address instead of blocking them. While the redirects aren’t encrypted either, many browsers don’t care. They simply follow the redirect, fail to reach a server and display an error message instead of the ad. To do that, enable logging to figure out which requests get blocked by Privoxy and add the hosts (no path patterns) to a section like this: {+redirect{http://127.0.0.1:0/} -block -limit-connect} .ivwbox.de:443/ Additionally you have to configure your browser to contact “127.0.0.1:0” directly (instead of through Privoxy). To add a proxy exception in Mozilla Firefox open the “Preferences”, click the “Settings” button located
Related Questions
- On some HTTPS sites my browser warns me about unauthenticated content, the URL bar doesn get highlighted and the lock symbol appears to be broken. Whats going on?
- Suppose you enter a URL of http://www.cs.camosun.bc.ca/~langs/funstuff.html in the browsers address bar. How does the browser find out where to look?
- Should I trust a website that contains unauthenticated content but is still an https?
