What's Fastly default behavior with objects larger than 5GB?


I know Fastly cannot cache object larger than 5GB, but can it still proxy them? Does it have to GET the whole object before delivering it?

What’s Fastly behavior with such large objects?



If you enable streaming miss for your large files, the files should be delivered as the bytes are received (you won’t need to wait for the entire object to complete before delivering to your end users). Give it a try:



If you don’t have streaming miss enabled, you get an unbranded vanilla varnish 503 error. That’s what started us down the road of “Hey, wait…what…” in our own diagnostic, leading me to ask earlier how to redirect based on a Content-Length: header in the beresp. :slight_smile: Anyone got any ideas? Chime in!