Compare commits
1
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
832a7e6fe6 |
No files matched your search
@@ -2479,7 +2479,7 @@ It refuses a request with `431` for any of:
|
||||
- more than 100 header fields. A header sent twice counts twice. `Host` and
|
||||
`Transfer-Encoding` do not count. `X-Request-ID` and `X-Forwarded-Proto` do.
|
||||
|
||||
Real clients never reach these limits. nginx refuses lines over 8 KiB by
|
||||
Real clients rarely reach these limits. nginx refuses lines over 8 KiB by
|
||||
default, and Apache's default limit is about the same. The answer is `deny`. The
|
||||
log line's action is `request_line_too_long` for `414` and
|
||||
`request_header_too_large` for `431`. The refusal makes no ban and is no
|
||||
@@ -2498,9 +2498,9 @@ other check runs on it.
|
||||
|
||||
The Core Rule Set runs each of its rules on each cookie, so thousands of small
|
||||
cookies would keep it busy for over a second. One 30 KB cookie or query string
|
||||
would keep it busy for a third of a second or more. Within the limits, a request
|
||||
takes less of its time. Enough such requests at once can still overload `waf`
|
||||
past `SWW_RPROXY_WAF_BACKEND_TIMEOUT_MS`.
|
||||
would keep it busy for a third of a second or more. A request within the limits
|
||||
keeps the Core Rule Set busy for less time. Enough such requests at once can
|
||||
still overload `waf` past `SWW_RPROXY_WAF_BACKEND_TIMEOUT_MS`.
|
||||
|
||||
### The report
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ import (
|
||||
|
||||
// The header limits: the most cookies and header fields a request may have,
|
||||
// and the longest its request line and each header line may be, in bytes, not
|
||||
// counting the line ending. Real clients never reach them. maxLineBytes is
|
||||
// counting the line ending. Real clients rarely reach them. maxLineBytes is
|
||||
// what nginx allows by default.
|
||||
const (
|
||||
maxCookies = 50
|
||||
|
||||
Reference in new issue
Block a user