Comments on: Polipo and uncachable file

By: Philip

Philip — Sat, 21 Jan 2012 12:59:00 +0000

I can confirm that ‘uncachable’ doesn’t work for me either. I’m using polipo 1.0.4 on OSX 10.6.8 via macports.

Removed my config file to ensure that I was using default settings. Confirmed with ‘polipo -v’ that my cachable file was found. Like ghostbar, I confirmed that my uncachable file format was correct by renaming the file to ‘forbidden’. Checked both with & without a forbidden file in existence, just in case.Ended up adding a few domains to my system proxy setting, not to the browser settings. On OSX, so I don’t know how to do the same on debian.

By: Jose Luis Rivas

Jose Luis Rivas — Mon, 07 Nov 2011 13:58:00 +0000

Yes Alan, I know this but I need my notebook and my wife’s notebook to work the same and I thought it would be easy to just configure it on polipo’s side than in each client. :-)

However, Thanks for your answer!

By: Alan Jenkins

Alan Jenkins — Mon, 07 Nov 2011 11:49:00 +0000

That is, the manual isn’t clear on whether “uncachable” entries override RelaxTransparency. Just a thought.

You can work around this in individual browsers. I think it’s called “no_proxy” (the environment variable): a list of domains which skip the proxy. Firefox lets you configure it in the GUI. I think Konqueror & Chrome under KDE do as well… I guess it’s fairly common, because of the desire to exclude localhost from being proxied.

By: Alan Jenkins

Alan Jenkins — Mon, 07 Nov 2011 11:44:00 +0000

“A number of websites incorrectly mark variable resources as cachable; such issues can be worked around in polipo by manually marking given categories of objects as uncachable.”