From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-www <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: ML archives caching 404 results |
Date: | 2014-10-07 14:03:44 |
Message-ID: | 22668.1412690624@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Tue, Oct 7, 2014 at 3:52 PM, Marti Raudsepp <marti(at)juffo(dot)org> wrote:
>> When adding my messages to CommitFest, I noticed that when I'm fast enough
>> to click on the resulting link, I get a 404 page from mailing list archives,
>> I guess if archives loader hasn't processed my message yet. This 404 result
>> gets cached for a long time, so my message is not viewable even after links
>> to it appear in archives.
FWIW, I've been annoyed by that too ...
>> Is there a default expiration time set in Varnish somewhere? Maybe the
>> solution is as easy as setting a lower TTL for 404 results in Varnish:
>> http://www.garron.me/en/bits/avoid-varnish-cache-404-error-page.html
> Yes we cache the 404 pages, and that's definitely intentional.
It might be intentional, but is it really useful? How much traffic do
we get to nonexistent pages?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2014-10-07 14:06:46 | Re: ML archives caching 404 results |
Previous Message | Magnus Hagander | 2014-10-07 13:57:07 | Re: ML archives caching 404 results |