Skip to content

docs: clarify parts limit behavior #1430

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vibhor-aggr wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify parts limit behavior #1430

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,6 +283,10 @@ Key | Description | Default
`headerPairs` | For multipart forms, the max number of header key=>value pairs to parse | 2000
`fieldNestingDepth` | Max number of nesting levels for field names (e.g. `a[b][c]` has 2 levels) | Infinity

The `parts` limit is triggered when busboy reaches the configured number of
parts, not only after that number is exceeded. If you want to allow an exact
number of fields and files, set `parts` to at least one more than that total.

Specifying the limits can help protect your site against denial of service (DoS) attacks.

### `fileFilter`
Expand Down