Hi folks, We've been hearing reports of intermittent issues with broken partial downloads via our content delivery network, Fastly, from cdn.NetBSD.org, nycdn.NetBSD.org, and/or archive.NetBSD.org, particularly of large files like the installer images.
These issues are hard to track down because Fastly might choose a different cache each time, and maybe one cache has a problem while other nearby ones don't. With the HTTP header field `Fastly-Debug: true', Fastly will return some extra data in the response header that might help diagnose the problem. So if you catch a partially failed download with, e.g., curl -H 'Fastly-Debug: true' -D header.txt -O https://archive.NetBSD.org/... then it would be helpful to us if you could pass on the header.txt file that curl produces, along with the exact length of the data that curl was able to retrieve -- either by email, or by a PR filed with gnats at https://gnats.NetBSD.org or send-pr(1). Thanks, -Riastradh
