Hi (again),
Consecutive `apt update` invocations lead to alternating requests to the
mirrorlist location. In the original report is one of them: incorrect
If-Range date is responded with 200 OK and the full content. Here is a
sample of the other case of the alternation when If-Range is correct
date of last modification, so the HTTP server tries to satisfy the
Range: header. The file in auxfiles/ is updated with the current time
and in the next `apt update` this incorrect date will be used (like in
the original report).
Fetching https://fire.tower.3.bg/debian-mirrorlist.txt
to /var/lib/apt/lists/auxfiles/fire.tower.3.bg_debian-mirrorlist.txt
Queue is: https:fire.tower.3.bg
GET /debian-mirrorlist.txt HTTP/1.1
Host: fire.tower.3.bg
Range: bytes=1673-
If-Range: Sat, 02 Nov 2024 13:05:14 GMT
User-Agent: Debian APT-HTTP/1.3 (2.9.10)
Answer for: https://fire.tower.3.bg/debian-mirrorlist.txt
HTTP/1.1 416 Requested Range Not Satisfiable
Server: nginx
Date: Sun, 03 Nov 2024 08:22:26 GMT
Content-Type: text/html
Content-Length: 190
Connection: keep-alive
Content-Range: bytes */1673
Best regards,
Ognyan
