Re: ML archives caching 404 results

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-www <pgsql-www(at)postgresql(dot)org>
Subject: Re: ML archives caching 404 results
Date: 2014-10-07 14:06:58
Message-ID: CABRT9RBQLCCtwqkEzHR4VoAZ8zX3BUCDqi2y03C1Lm54_jJe0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Tue, Oct 7, 2014 at 4:57 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> The default is 4 hours though, which might be a bit of an
> overkill. But how should would it have to be to deal with the scenario
> you're outlining?

Ideally it would appear immediately, but something like 10 minutes
would be a lot less annoying than 4 hours.

>> Another solution would be to somehow shoehorn a cache key into 404 result
>> pages, but that smells of hack
> Yeah, that's definitely ugly. We could do something like "purge all
> 404's whenever a new email arrives", but that seems quite ugly...

Can we purge by URL from pgarchives like we do in pgweb? We could go
"simple and stupid" and just purge /message-id/.../ on the receipt of
any message.

Regards,
Marti

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2014-10-07 14:24:48 Re: ML archives caching 404 results
Previous Message Magnus Hagander 2014-10-07 14:06:46 Re: ML archives caching 404 results