I'm facing an issue with our Application Gateway that denies PUT requests exceeding 128 kb, and I keep getting a '413 Content Too Large' error. This isn't about file uploads; it's just a straightforward PUT request containing a payload. We're using the WAF V2 tier and following OWASP 3.0 standards.
In my troubleshooting, I switched the WAF to detection mode and even disabled it completely (in a non-production environment), but nothing changed. I also checked the policy settings, where the 'Maximum request body size (KB)' is limited to 128 kb, which is already at its max. I tried disabling the 'Enforce request body inspection' option, but that didn't help either.
Is this a limitation of the Application Gateway or the WAF version we're using? Is there any workaround for this?
**UPDATE:** I initially thought the issue stemmed from the backend server, but it turned out to be related to a WAF configuration error on my part. Once I disabled the 'Enforce request body inspection' on the correct WAF, the problem was resolved.
2 Answers
It sounds like you're on the right track. Definitely check those access logs on the Application Gateway to see if the server status matches up with your HTTP status codes. Sometimes the proxy can mask what's actually going wrong on the server side.
Glad you figured it out! It can be tricky with two WAFs involved. Just make sure all settings are aligned before making changes—this can save you a lot of headaches. If issues persist after the fix, it might still be worth revisiting the logs for deeper insights.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Fix Not Being Able To Add New Categories With Intuitive Category Checklist For Wordpress
Get Real User IP Without Installing Cloudflare Apache Module
How to Get Total Line Count In Visual Studio 2013 Without Addons
Install and Configure PhpMyAdmin on Centos 7
How To Setup PostfixAdmin With Dovecot and Postfix Virtual Mailbox