You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,8 @@ The following emojis are used to highlight certain changes:
16
16
### Added
17
17
18
18
- Add `--max-request-duration` CLI flag (`RAINBOW_MAX_REQUEST_DURATION` env var) to configure the Boxo gateway `MaxRequestDuration` option. Defaults to 1 hour, matching Boxo's DefaultMaxRequestDuration. ([#350](https://github.com/ipfs/rainbow/pull/350))
19
+
- Add `--max-deserialized-response-size` (`RAINBOW_MAX_DESERIALIZED_RESPONSE_SIZE`) to limit deserialized responses by content size. Trustless formats (raw, CAR) are not affected. ([#362](https://github.com/ipfs/rainbow/pull/362))
20
+
- Add `--max-unixfs-dag-response-size` (`RAINBOW_MAX_UNIXFS_DAG_RESPONSE_SIZE`) to limit all response formats by UnixFS DAG size, including raw blocks, CAR, and TAR. ([#362](https://github.com/ipfs/rainbow/pull/362))
0 commit comments