#3126 caching headers for repos.fedorapeople.org appear wrong
Closed: Fixed None Opened 12 years ago by jsanders.

= bug description =
I think that the headers delivered in http requests to repos.fedorapeople.org don't have the correct caching attributes. I'm having a problem updating using http://repos.fedorapeople.org/repos/spot/chromium/ through a squid proxy. Through the proxy I only get old versions of the repo database files. Unsetting the proxy it works.

= bug analysis =
If I do (without a proxy):
{{{
$ wget -S http://repos.fedorapeople.org/repos/spot/chromium/fedora-16/x86_64/repodata/a211d9faff7e87a6ef06cd199430cef99f6c977e99e1b65bb13efab9c9983152-primary.xml.gz
}}}
There is no Cache-Control header here and the expiry date appears unset.

The documentation for mirroring a file from fedora suggest that the following is used to serve repo files:

{{{
http://fedoraproject.org/wiki/Infrastructure/Mirroring
<LocationMatch "\.(xml|xml\.gz|xml\.asc|sqlite)$">
Header set Cache-Control "must-revalidate"
ExpiresActive On
ExpiresDefault "now"
</LocationMatch>
}}}

= fix recommendation =
I would modify the configuration for the server for repos.fedorapeople.org is modified to follow what is suggested in
http://fedoraproject.org/wiki/Infrastructure/Mirroring
(Caching of metadata)


ok. I commited a variant of this:

<LocationMatch "/repos/.*\.(xml|xml\.gz|xml\.asc|sqlite.+)$">

since we only have repos under /repos, and since sqlite.* can be a part of it.

Can you confirm it looks as you expect now and reopen if you see any problems?

Thanks for the suggestion!

Login to comment on this ticket.

Metadata