Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 24 replies
  • Subscribers 33 subscribers
  • Views 17321 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Having Problems with WAF with Nextcloud behind it. Error: "413 Request Entity too large"

Dwayne Parker

Hi,

 

I am using a Nextcloud behind a XG with WAF enabled. This worked until version 18 of XG. Now I am getting 413 Request Enitity too large Errors as soon as I am enabling "Common threat filter", Antivirus or Cookie Signing in the Protection Policy.

The WebServerProtection Log's in XG are showing the requests as allowed, but with HTTP Status Code 413. In the Logs of the server, there's nothing found.

Could someone advise me how to fix this?

 

P.S. After some research, I've read in the Nextcloud Forums that if a NGINX Reverseproxy is used, the configuration key "client_max_body_size" has to be set to a higher value.



This thread was automatically locked due to age.
Parents
  • 0

    XG WAF does not support WebDAV.

    In v18 we updated the ModSecurity and OWASP rules, and it's likely that this tightening of security has impacted on the previously working configuration, however we did not support WebDAV in versions earlier than v18, and we still do not.

     

    Regards,

    Stuart 

Reply
  • 0

    XG WAF does not support WebDAV.

    In v18 we updated the ModSecurity and OWASP rules, and it's likely that this tightening of security has impacted on the previously working configuration, however we did not support WebDAV in versions earlier than v18, and we still do not.

     

    Regards,

    Stuart 

Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?