413 Request entity too large

Question

In the WAF configuration If an user upload a file greater than 1 Mb receives the error Request body no files data length is larger than the configured limit - 413 Request entity too large 
 
 I found in the UTM you can modify the squid.conf-default, but I didn&acute;t fine anythig about th XG. 
 
 Someone will know how to increase the Mb??

Chuck Smith · Accepted Answer

I've spoken to some people in some pretty high places and I'm still waiting to hear from someone at the very very top. 
 So as of the time of this post the only thing we can currently do to get this applied and working is to manually update the db record and force an update to the waf_reconfig. 
 
 First is that you need to know all of the exclusions(skips) you'll need to enter into the policy under the GUI. 
 Add them them in and then save the policy. 
 
 You also need to know the policy ID, so you would run: psql -U nobody -d corporate -c "select * from tblwafsecurityprofile;" 
 (my query returns) 
 
 Look for the number at the beginning of the line listing your policy, in my case the ID I'm interested in is 7. 
 Next you'd need to apply the change to the value in the sec_request_body_no_files_limit record. in my case I'm defining it to be 10MB and I'm telling the query to apply it to policy ID = 7 
 psql -U nobody -d corporate -c "update tblwafsecurityprofile set sec_request_body_no_files_limit ="10485760" where id ="7";" 
 Then finally you need to force the system to update the important files with: 
 opcode waf_reconfig -t json -b '{"Entity": "waf_advanced_config", "Event": "UPDATE"}' -ds nosync 
 This will rebuild the reverseporxy.conf and get the WAF up and running with the new larger limit.. 
 After this is done, If you make ANY changes to this policy in the GUI you will need to do the above process again because the default 1048576 value will be reinserted into the db and reverseproxy.conf bringing you back to the broken and unusable 413 issue.

eriikooz · Answer

I have the same problem. How can i update the psql DB as a temporary fix? 
 EDIT: I found it and it works! 
 You also need to know the policy ID, so you would run: psql -U nobody -d corporate -c "select * from tblwafsecurityprofile;"

Look for the number at the beginning of the line listing your policy, in my case the ID I'm interested in is 7.

Next you'd need to apply the change to the value in the sec_request_body_no_files_limit record. in my case I'm defining it to be 10MB and I'm telling the query to apply it to policy ID = 7

psql -U nobody -d corporate -c "update tblwafsecurityprofile set sec_request_body_no_files_limit ="10485760" where id ="7";"

Then finally you need to force the system to update the important files with:

opcode waf_reconfig -t json -b '{"Entity": "waf_advanced_config", "Event": "UPDATE"}' -ds nosync

This will rebuild the reverseporxy.conf and get the WAF up and running with the new larger limit.. 

After this is done, If you make ANY changes to this policy in the GUI you will need to do the above process again because the default 1048576 value will be reinserted into the db and reverseproxy.conf bringing you back to the broken and unusable 413 issue.

Jessica Lopez · Answer

Hi 
 We also have a remote sesion with support, and also he use the commands you mention: 
 
 "We run the following commands in the XG to increase the file size allowed in the WAF from 1048576 [1MB] to 52428800 [50MB]. With the following command: 
 SFVUNL_VM01_SFOS 17.5.7 MR-7# psql -U nobody -d corporate -c "update tblwafsecur ityprofile set sec_request_body_no_files_limit ="52428800" where id ="7";" UPDATE 1 . SFVUNL_VM01_SFOS 17.5.7 MR-7# opcode waf_reconfig -t json -b '{"Entity": "waf_ad vanced_config", "Event": "UPDATE"}' -ds nosync 200 OK { "status": "200", "statusmessage": "success" } . SFVUNL_VM01_SFOS 17.5.7 MR-7# psql -U nobody -d corporate -c "select name,id,sec _request_body_no_files_limit from tblwafsecurityprofile;" name | id | sec_request_body_no_files_limit ---------------------------+----+--------------------------------- Exchange AutoDiscover | 1 | 1048576 Exchange General | 2 | 1048576 Microsoft Lync | 4 | 1048576 Microsoft RDG 2008 | 5 | 1048576 Microsoft RD Web 2008 | 6 | 1048576 Exchange Outlook Anywhere | 3 | 1048576 WAF Police | 7 | 52428800 
 
 but we got the error again with files of more than 49KB, smaller than these worked fine. 
 
 On the IIS we increase this value "" uploadReadAheadSize "which by default is -49KB to a larger one, after this all the files that failed previously it was possible to load them, although with 30MB files this still failed, but this change lets us see that the problem indicates that it is a configuration in the IIS that needs to be changed." 
 
 So we&acute;re waiting for the reply to this, because if we try to upload a file without passing through the WAF, and we did&acute;t have this problem. 
 I&acute;ll let you know

413 Request entity too large

Top Replies