Opened 2 years ago

Closed 23 months ago

Last modified 23 months ago

#876 closed defect (fixed)

"request entity too large message" when connecting to an apache server with ModSecurity

Reported by: korsani Owned by:
Priority: major Milestone: 2.9
Component: Add Blog/Site Version: 2.8
Keywords: Cc:

Description

Hi,
I have a standalone wordpress installation self-hosted by lws (https://www.lws.fr/). I almost can't touch the apache' conf.
When I connect to it with the iPhone wordpress client, it returns me "HTTP/1.1 413 Request Entity Too Large"
Here is what says error.logs :
[Tue May 31 01:38:21 2011] [error] [client 82.230.17.116] ModSecurity?: Access denied with code 413 (phase 2). Match of "rx 0$" against "REQUEST_HEADERS:Content-Length" required. [file "/etc/apache2/modsecurity/rules/modsecurity_crs_21_protocol_anomalies.conf"] [line "83"] [id "960904"] [rev "2.1.2"] [msg "Request Containing Content, but Missing Content-Type header"] [severity "NOTICE"] [hostname "www.malungos-paris.com"] [uri "/blog/wp-login.php"] [unique_id "foo"]
[Tue May 31 01:38:41 2011] [error] [client 82.230.17.116] ModSecurity?: Access denied with code 413 (phase 2). Match of "rx
0$" against "REQUEST_HEADERS:Content-Length" required. [file "/etc/apache2/modsecurity/rules/modsecurity_crs_21_protocol_anomalies.conf"] [line "83"] [id "960904"] [rev "2.1.2"] [msg "Request Containing Content, but Missing Content-Type header"] [severity "NOTICE"] [hostname "www.malungos-paris.com"] [uri "/blog/xmlrpc.php"] [unique_id "foo"]
I have an other standalone wordpress installation, but not hosted : I own it, I have full power on apache' conf, and I don't have this error (and ModSecurity? is not installed ;) ).

I put the priority of this bug to 'blocker', as I can't use the iPhone client to update the blog ...

Attachments (1)

error.logs (939 bytes) - added by korsani 2 years ago.

Download all attachments as: .zip

Change History (5)

Changed 2 years ago by korsani

comment:1 Changed 2 years ago by korsani

  • Summary changed from "request entity too large message" when connection to an apache server with ModSecurity to "request entity too large message" when connecting to an apache server with ModSecurity

comment:2 Changed 23 months ago by koke

  • Milestone changed from 3.0 to 2.9
  • Priority changed from blocker to major

comment:3 Changed 23 months ago by koke

  • Resolution set to fixed
  • Status changed from new to closed

(In [2124]) Set Content-Length for requests with POST data. Fixes #876 (should fix it)

comment:4 Changed 23 months ago by koke

Last commit should probably fix it, although looking at the log, we only hit wp-login.php on post preview, and all calls to xmlrpc.php were already using content-length.

Note: See TracTickets for help on using tickets.