English, Software, Tecnología

Polipo and uncachable file

Posted by on November 5, 2011 at 3:47 pm.

Dear lazyweb,

I was searching through the internet what was I doing wrong, I wrote to the polipo-user list but my email got stuck on moderation, and my connection is really shitty (that’s why I’m using polipo the way I’m using it). I have relaxTransparency and mindlesslyCacheVary set to true, but I don’t need so aggresive caching in my development stages that are located under *.local and another development subdomain on the net.

Already tried setting uncachableFile to /etc/polipo/uncachable and to ~/.polipo-uncachable, according to the web-config thing is properly setted up, but can’t get it to recognize it’s content. I first thought it was I was writing bad the regex, .*\.local but it does work in the /etc/polipo/forbidden file. Besides, adding complete domains to the uncachable file doesn’t works neither. Could someone confirm this or throw me a hand on this? I’m using 1.0.4.1-1.1 version which is the last one on unstable repos.

  • Alan Jenkins

    “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.”

    • Alan Jenkins

      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.

      • http://www.joseluisrivas.net Jose Luis Rivas

        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!

  • Philip

    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.