make static cache policy explicit, disable caching for objects >100 MiB #3067
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When trying to download bigger archives, I saw some errors:
or
After a little digging I saw that the connection between fastly & nginx is cut after streaming exactly 100 MiB,
which made me think about limits :)
Then :
For now I chose to just forbid caching when the file is too big, segmented caching would be a little more effort, with IMO limited short-term gain. These archives aren't downloaded that often.