Allan McRae <al...@archlinux.org> on Mon, 2022/09/26 20:44: > On 19/9/22 22:52, Christian Hesse wrote: > > From: Christian Hesse <m...@eworm.de> > > > > By setting the HTTP header 'Cache-Control: no-cache' when returning with > > the status code 404 (not found) the server can indicate that this is a > > soft failure. No error message is shown, and server's error count is > > not increased. > > > > This can be used by servers that are not expected to be complete, for > > example when serving a local cache [0]. In nginx this can be achived by > > adding a single directive in location block: > > > > add_header Cache-Control "no-cache"; > > I am not accepting this patch. > 1) "no-cache" to indicate this a cache of packages...
You missed the point. This does not tell not to cache packages.
It does tell not to cache an error. ;)
Fun fact: Searching for the keywords yields a lot of matches for some well
known cloud providers and their proxy software. Looks like the same is used
there not to cache errors.
> 2) using a directive that has a completely different meaning.
So still unanswered... Could there be a directive that we can agree on?
Anyway - still expected. :-p
So hoping for the CacheServer thing now.
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
pgp6KKsE5xmnp.pgp
Description: OpenPGP digital signature
