feat(gateway): add MaxRangeRequestFileSize protection #1043
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.
Adds Config.MaxRangeRequestFileSize to protect against CDN issues with large file range requests. when set, range requests for files larger than this limit return HTTP 501 with suggestion to use verifiable block requests (application/vnd.ipld.raw).
Intention here is to protect against Cloudflare's issue where range requests for files over 5GiB are silently ignored, causing entire file to be returned instead of requested range, leading to excess bandwidth and billing.
The fix here shouldengage when cloudflare sends very first range request to boxo/gateway backend. The backend is able to detect range request for a file beyond safe size, and refuse responding.