feat(config): optional Gateway.MaxRangeRequestFileSize#10997
Merged
feat(config): optional Gateway.MaxRangeRequestFileSize#10997
Conversation
adds Gateway.MaxRangeRequestFileSize configuration to protect against CDN bugs where range requests over certain sizes return entire files instead of requested byte ranges, causing unexpected bandwidth costs. - default: 0 (no limit) - returns 501 Not Implemented for oversized range requests - protects against CDNs like Cloudflare that ignore range requests over 5GiB also introduces OptionalBytes type to reduce code duplication when handling byte-size configuration values, replacing manual string parsing with humanize.ParseBytes. migrates existing byte-size configs to use this new type. Fixes: ipfs/boxo#856
This was referenced Sep 29, 2025
Closed
guillaumemichel
approved these changes
Oct 7, 2025
gammazero
approved these changes
Nov 12, 2025
Member
Author
|
@Brent-Sanchez are you sure you commented on correct PR? Confused that you mean by diagnostics. Both diagnostic screen in webui and telemetry in Kubo were documented in changelog and release notes and there is telemetry.md in docs directory as well, with instruction how to disable the telemetry. Hope this helps. ps. Mind that commenting on closed PR is usually ignored, I've seen your question by sheer luck, next time open a topic in https://discuss.ipfs.tech/ :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR adds Gateway.MaxRangeRequestFileSize configuration to protect against CDN bugs where range requests over certain sizes return entire files instead of requested byte ranges, causing unexpected bandwidth costs.
0(no limit)501 Not Implementedfor oversized range requestsalso introduces OptionalBytes type to reduce code duplication when handling byte-size configuration values, replacing manual string parsing with humanize.ParseBytes. migrates existing byte-size configs to use this new type.