AW: WG: Snapshot.debian.org: "503 Response object too large" issue prevents retrieval of files exceeding 2GB
Hi Philipp,
On 6/10/25 22:45 PM, Phillipp Kern wrote:
> On 6/10/25 12:54 PM, Warlich, Christof wrote:
> > I encountered a severe usability limitation with snapshot.debian.org concerning packages whose source archives exceed ~2GB in size. Such files systematically fail with the error "503 Response object too large," rendering the affected files effectively impossible to download.
> This is now fixed. There was a config difference between deb.d.o and snapshot.d.o that caused this, my apologies.
many thanks for the quick fix, works like a charm.
Cheers,
Chris
Hi Christof,
On 6/10/25 12:54 PM, Warlich, Christof wrote:
> I encountered a severe usability limitation with snapshot.debian.org concerning packages whose source archives exceed ~2GB in size. Such files systematically fail with the error "503 Response object too large," rendering the affected files effectively impossible to download.
This is now fixed. There was a config difference between deb.d.o and snapshot.d.o that caused this, my apologies.
Generally Fastly requires to turn on segmented caching[1] to serve larger objects. However our account still supports 2 GB for requests without Streaming Miss (snapshot.d.o) and 5 GB for requests with Streaming Miss (deb.d.o). I turned on Streaming Miss now, which fixed the issue.
Kind regards and thanks for the report
Philipp Kern
[1]
https://www.fastly.com/documentation/guides/full-site-delivery/caching/segmented-caching/
Reply to: