Re: Fwd: Fwd: Accessing git.kernel.org by browser results in infinite refresh loop

On Sun, Jan 17, 2010 at 1:57 PM, Richard Zidlicky <[email protected]> wrote:
> Hi,
>
> did you tweak your polipo config in some way? For me it allways worked fine
> with the kernel.org git. I did have problems because I used a proxy chain
> wwwoffle->polipo and had to adjust something on wwwoffle.
> Now I have polipo with essentially default settings and it works.

    Yes I've played with the configs, but I don't suspect any problem
in the config. Below are my settings (that involve caching):
    * mindlesslyCacheVary = false
    * cacheIsShared = true
    * cacheIsShared = false (but no cookies involved);
    * dontCacheRedirects = false (but no redirects involved);


> Also just noticed that kernel.org now returns a different "Expires" header
> than what your log shows so maybe the problem went away.

    Yes. First it returns a page with the "Expire: never" and with a
refresh in the HTML, and then after some time (maybe after the content
has been generated on the server), (but on a new request) it gives a
valid response (with Expire to sensible value) and some real content.
    (Just try different commits in curl, but not those tried in the
browser, as the server would have already generated the content.)


> I do not think that "Expires: never" means it is reasonable to assume the page
> never ever changes.

   Yes, but it at least means: "the page will not modify for one minute"...


> Richard

    Thanks,
    Ciprian.

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev