Thanks Frédéric for your report.
In CC, mirror.peer1.net people.
The complete bug history is available at http://bugs.debian.org/571751
In short,the Last-Modified seen by the CDN/HTTP daemon is not always
consistent with the actual mtime of the file.
On Sat, Feb 27, 2010 at 01:38:50PM -0500, Frédéric Brière wrote:
> Package: mirrors
> Severity: normal
>
> mirror.peer1.net sometimes returns cached files that don't mesh with the
> rest of the archive. For example, here's part of an apt-get run:
>
> GET /debian/dists/sid/Release HTTP/1.1
> If-Modified-Since: Fri, 26 Feb 2010 03:26:20 GMT
[..]
> HTTP/1.1 304 Not Modified
> Date: Sat, 27 Feb 2010 17:12:46 GMT
> Last-Modified: Fri, 26 Feb 2010 03:26:20 GMT
[...]
> But fetching Release manually returns a much newer file:
> Origin: Debian
> Label: Debian
> Suite: unstable
> Codename: sid
> Date: Sat, 27 Feb 2010 03:07:23 UTC
> [...]
>
> The contents of the archive matches this new version, and apt-get
> obviously complains when the various files don't correspond to their
> previous checksum.
I cannot reproduce today, whatever is the peer1 backend.
Indeed, the Last-modified of the file is the one expected "28 Feb 2010 03:20:45
GMT" and
the HTTP code returned is the one expected (i.e. 200 OK with
If-Modified-Since is before this date, 304 Not Modified if after this
date).
for ip in $(dig +short mirror.peer1.net);
do echo $ip ;
wget -O /dev/null -S --header="Host: mirror.peer1.net" \
--header="If-Modified-Since: Fri, 28 Feb 2010 03:26:20 GMT" \
http://$ip/debian/dists/sid/Release
done
--
Simon Paillard
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
