FS#65046 - Arch Linux Archive returns improper 302 redirect responses
Attached to Project:
Arch Linux
Opened by Andrei Pozolotin (random-archer) - Saturday, 04 January 2020, 17:21 GMT
Last edited by Christian Heusel (gromit) - Friday, 24 November 2023, 17:45 GMT
Opened by Andrei Pozolotin (random-archer) - Saturday, 04 January 2020, 17:21 GMT
Last edited by Christian Heusel (gromit) - Friday, 24 November 2023, 17:45 GMT
|
Details
1. Arch Linux Archive:
https://wiki.archlinux.org/index.php/Arch_Linux_Archive returns improper 302 redirect responses, which has no "Expires" or "Cache-Control" headers, and which therefore can not be properly cached by squid, consequently resulting in repeated needless hits on the archive server 2. the problem is confirmed by squid developers: http://lists.squid-cache.org/pipermail/squid-users/2020-January/021586.html http://lists.squid-cache.org/pipermail/squid-users/2020-January/021587.html http://lists.squid-cache.org/pipermail/squid-users/2020-January/021592.html 3. the solution is to add standard HTTP "Expires" and/or "Cache-Control" headers when generating responses for repository requests: https://archive.archlinux.org/repos/* |
This task depends upon
Closed by Christian Heusel (gromit)
Friday, 24 November 2023, 17:45 GMT
Reason for closing: Won't fix
Friday, 24 November 2023, 17:45 GMT
Reason for closing: Won't fix
Comment by
Sven-Hendrik Haase (Svenstaro) -
Wednesday, 12 February 2020, 11:41 GMT
Comment by
Sven-Hendrik Haase (Svenstaro) -
Friday, 30 December 2022, 08:13 GMT
Comment by
Evangelos Foutras (foutrelis) -
Friday, 30 December 2022, 16:18 GMT
Comment by
Buggy McBugFace (bugbot) - Tuesday,
08 August 2023, 19:11 GMT
I have no idea about the archive but I added some people who might
know.
Can you guys check this one out please?
Regardless of what we do, archive.org's redirect will still be
uncacheable (unless I'm missing something). Therefore, we might as
well leave it as-is for consistency. :)
This is an automated comment as this bug is open for more then 2
years. Please reply if you still experience this bug otherwise
this issue will be closed after 1 month.