- 最新
- 投票最多
- 评论最多
Hi, I would agree with you on the fact that it's probably a bug, on which you may need to open a ticket to get it fixed.
In the meantime, to go around it, you may want (if your security constraints allow) to create WAF rules specific to large content having the option "Continue" associated with other conditions when its ok to go forward . WAF will then only inspect the first 8'192 bytes and accept the request if those initial bytes don't show any issue and the other conditions are satisfied.
For rules on oversize content, see https://docs.aws.amazon.com/waf/latest/developerguide/waf-oversize-request-components.html
Hope it helps
Didier
Hello. We believe this issue has been resolved at this time.
I have contacted AWS technical support regarding this issue and they have responded that they are already aware of this bug issue and will be working on a fix.
I believe this bug has been fixed as I have now tried and could not reproduce it.
相关内容
- AWS 官方已更新 7 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
Hi, I have also experienced this phenomenon. I couldn't find a Q&A on this phenomenon anywhere and came across it here. I tried your answer, but the "413 (Payload Too Large)" error continued to occur. Is there anything wrong with the following that I have tried?
Creating a custom rule to AWS WAF Field to match: Body Match type: Size greater than Size: 16,384 Text transformations: None (Priority 0) Oversize handling: Continue Action: Count
WAF also has a custom rule for Block with Action after Priority 1.