Bump client_body_buffer_size to 16k #12
Merged
Conversation
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
Drop the overzealous 1k buffer size limit on body and header buffers. 16k default is safe: we have memory these days.
bennettgoble
changed the title
bennettgoble
commented
Jan 13, 2024
| @@ -33,10 +33,6 @@ http { | |||
| # Disable etag | |||
| etag off; | |||
|
|
|||
| # Lower buffer size to possibly prevent DoS attacks and buffer overflow vulnerabilities. | |||
| client_body_buffer_size 1k; | |||
| client_header_buffer_size 1k; | |||
There was a problem hiding this comment.
1k is the default for client_header_buffer_size already.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Drop the overzealous 1k buffer size limit on body buffer size. 16k default is safe: we have memory these days.