Skip to content
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

Jump to bottom

Fixing uri max size #1266

Merged
merged 2 commits into from
Feb 23, 2023
Merged

Fixing uri max size #1266

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f3a6461
Fixing uri max size
kawaiipantsu Feb 21, 2023
350179f
Added detailed comment
kawaiipantsu Feb 23, 2023
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
9 changes: 8 additions & 1 deletion docker/nginx/dist/conf/tpotweb.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,14 @@ server {
client_body_buffer_size 128k;
client_header_buffer_size 1k;
client_max_body_size 2M;
large_client_header_buffers 2 1k;

t3chn0m4g3 marked this conversation as resolved.
Show resolved Hide resolved
### Changed from OWASP recommendations: "2 1k" to "2 1280" (So 1.2k)
### When you pass though potentially another reverse proxy/load balancer
### in front of tpotce you can introduce more headers than normal and
### therefore you can exceed the allowed header buffer of 1k.
### An 280 extra bytes seems to be working for most use-cases.
### And still keeping it close to OWASP's recommendation.
large_client_header_buffers 2 1280;

### Mitigate Slow HHTP DoS Attack
### Timeouts definition ##
Expand Down