3 ms·
I read it and it's a design decision documented here: https://docs.aws.amazon.com/waf/latest/developerguide/waf-oversize-request-components.html https://docs.a
by threeseed 3y ago
I read it and it's a design decision documented here:
https://docs.aws.amazon.com/waf/latest/developerguide/waf-oversize-request-components.html https://docs.aws.amazon.com/waf/latest/developerguide/waf-ov...
For oversize requests WAF can be configured to reject it.
- diarrhea 3y agoTwo observations: 8KB is a small amount of data. Many apps will need more, so will not be able to blanket block these. Even 64k, what appears to be the absolute limit, might not be enough. Continuing, not blocking, is the default when not using the console, making this insecure by default.
- threeseed 3y agoYou should be using multi-part/chunked encoding for large file sizes as it helps prevents DDOS attacks. And having an insecure default is a huge difference from 100% of requests are allowed.