[pacman-dev] [PATCH 1/1] support http header to indicate an expected failure

Christian Hesse list at eworm.de
Wed May 26 08:22:52 UTC 2021

Andrew Gregory <andrew.gregory.8 at gmail.com> on Mon, 2021/05/24 11:50:
> On 05/24/21 at 08:31pm, Christian Hesse wrote:
> > Christian Hesse <list at eworm.de> on Fri, 2021/05/21 10:06:  
> > > By setting an extra HTTP header 'X-Pacman-Expected-Failure' the server
> > > can indicate that the failure is expected. The next server is tried
> > > without error message and without increasing the server's error count.
> > > 
> > > This can be used by servers that are not expected to be complete, for
> > > example when serving a local cache.  
> > 
> > Any comment on this?
> > Where to document the behavior?
> > 
> > BTW, this is the matching branch for pacredir:
> > https://github.com/eworm-de/pacredir/commits/404-header  
> I'm not a fan of having this be server-side.

Would be a perfect fit for me and my use case. :-p

For those interested... I created simple flow charts to describe what happens
when pacman sends its requests to pacredir.

In the seconds chart pacredir returns the http code 404 to pacman just before
the mirror is contacted. That is where the extra header should be included.

> I'd rather see
> https://bugs.archlinux.org/task/23407 implemented.

Could work as well.
But note that pacredir does handle database files as well. So limiting
'CacheServer' to package files would restrict pacredir's functionality.
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);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/pacman-dev/attachments/20210526/26b047b8/attachment.sig>

More information about the pacman-dev mailing list