How can we improve Azure Networking?

Azure Application Gateway WAF Mode Increase Limit on SecRequestBodyLimit

When we have the WAF set to prevention mode some of our HTTP post are denied with code 413.

Request body no files data length is larger than the configured limit (131072).. Deny with code (413)

Can you make these two settings configurable on the WAF?



289 votes
Sign in
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Mark Kurley shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Microsoft
Signed in as (Sign out)
  • Timothy Lee Russell commented  ·   ·  Flag as inappropriate

    Thanks for letting us know that there is a fix in the works.

    Any update on when we might expect the fix to this blocking issue? (Pun intended, I suppose.)

  • Tomasz S commented  ·   ·  Flag as inappropriate

    Could you let us know when this will be added? because of that limit we had to disable WAF

  • Daan commented  ·   ·  Flag as inappropriate

    Is this now implemented? Because the status is still planned I would also like to see that the message body could be bigger then 128KB

  • Joakim commented  ·   ·  Flag as inappropriate

    We desperately need to be able to configure the limit of the message body to be bigger than 128KB (131072). We run off-the-shelf software that cannot be changed to respect this limit. One exaplle is DotNetNuke/Evoq, where the Admin interface use a lot of XHR requests which break the size limit.

  • Joakim commented  ·   ·  Flag as inappropriate

    As far as I understand, this is now implemented, but the maximum limit is 128KB. This is still to low for some applications. We have COTS software that generetes POST request with large _VIEWSTATE that gets blocked with 413 ModSecurity Action. Please raise the max value.

  • Scott commented  ·   ·  Flag as inappropriate

    Could you give us an update on when this will be available (weeks, months, years)? And, maybe an update on the 20 Listener limit?

  • Anonymous commented  ·   ·  Flag as inappropriate

    The size of the 128 kb is ridiculously small. Due to this our entire move to the cloud for an active/paying customer has been on halt. In the meanwhile, if Microsoft support members can simply help the existing Azure customers by updating these parameter value in our WAF instance (within our subscription) then atleast we could go live and continue moving to Azure.

  • Jonathan Gonzalez commented  ·   ·  Flag as inappropriate

    At least, while implementing the parameterization of this rule, they should be able to be deactivated so that at least it would allow us to use the rest of the firewall rules.

Feedback and Knowledge Base