Skip to content

feat: add content size limit flags#364

Open
lidel wants to merge 2 commits intomainfrom
feat/max-response-size
Open

feat: add content size limit flags#364
lidel wants to merge 2 commits intomainfrom
feat/max-response-size

Conversation

@lidel
Copy link
Copy Markdown
Member

@lidel lidel commented Apr 10, 2026

Wire boxo gateway size limit options as opt-in flags:

  • --max-deserialized-response-size / RAINBOW_MAX_DESERIALIZED_RESPONSE_SIZE
  • --max-unixfs-dag-response-size / RAINBOW_MAX_UNIXFS_DAG_RESPONSE_SIZE

Both disabled by default (0). When set, content exceeding the limit returns 501 directing users to run their own IPFS node.

TODO

  • smoke test on rainbow staging

Wire boxo gateway size limit options as CLI flags:

- --max-deserialized-response-size / RAINBOW_MAX_DESERIALIZED_RESPONSE_SIZE
- --max-unixfs-dag-response-size / RAINBOW_MAX_UNIXFS_DAG_RESPONSE_SIZE

Both disabled by default (0). When set, content exceeding the limit
returns 501 directing users to run their own IPFS node.

Depends on ipfs/boxo#1138.
@lidel lidel force-pushed the feat/max-response-size branch from fb67d84 to 7e032af Compare April 10, 2026 16:03
@lidel lidel marked this pull request as ready for review April 10, 2026 18:21
@gammazero gammazero added the status/in-progress In progress label Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants