Ludovic Courtès writes:
> Hi!
>
> (“Sorry for the long delay” is officially my motto at this point.)
>
> Christopher Baines skribis:
>
>> This has been on my mind for a while, as I wonder what effect it has on
>> users fetching substitues.
>>
>> The narinfo caching as I understand it works as
BTW, one thing that would be interesting too is to return 404 with a
long ‘Cache-Control’ validity when the requested store item is among the
cached failures.
We could also add an extra response header to explicitly communicate
that the store item is known to fail to build.
Ludo’.
Hi!
(“Sorry for the long delay” is officially my motto at this point.)
Christopher Baines skribis:
> This has been on my mind for a while, as I wonder what effect it has on
> users fetching substitues.
>
> The narinfo caching as I understand it works as follows:
>
> Default success TTL => 36
Christopher Baines writes:
> This has been on my mind for a while, as I wonder what effect it has on
> users fetching substitues.
>
> The narinfo caching as I understand it works as follows:
>
> Default success TTL => 36 hours
> Negative TTL=> 1 hour
> Transient error TTL => 10
Hey,
This has been on my mind for a while, as I wonder what effect it has on
users fetching substitues.
The narinfo caching as I understand it works as follows:
Default success TTL => 36 hours
Negative TTL=> 1 hour
Transient error TTL => 10 minutes
I'm ignoring the success TTL, I'm
