Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C3C39EBF for ; Thu, 14 Jun 2012 06:01:48 +0000 (UTC) Received: (qmail 49231 invoked by uid 500); 14 Jun 2012 06:01:47 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 49025 invoked by uid 500); 14 Jun 2012 06:01:46 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Delivered-To: moderator for users@subversion.apache.org Received: (qmail 85513 invoked by uid 99); 14 Jun 2012 02:13:42 -0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) From: "HICHENS, David" To: "users@subversion.apache.org" Subject: Error 413 'Request entity too large' Thread-Topic: Error 413 'Request entity too large' Thread-Index: Ac1J0iSvYLzJzv2+RBuoQgvYmTQzQA== Date: Thu, 14 Jun 2012 02:13:02 +0000 Message-ID: <61547C9F299F644782DDC6AB44B008D8181A0EFE@mwlsvexm005.au.baesystems.com> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [150.207.3.185] Content-Type: multipart/alternative; boundary="_000_61547C9F299F644782DDC6AB44B008D8181A0EFEmwlsvexm005auba_" MIME-Version: 1.0 --_000_61547C9F299F644782DDC6AB44B008D8181A0EFEmwlsvexm005auba_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable After much wailing and nashing of teeth, I've finally resolved this error w= hich was preventing me adding large files to SVN. I tried many combinations= of 'LimitReqestBody' and 'LimitXMLRequestBody' Apache directives as sugges= ted by many Google search results without success. I belatedly checked the = Apache error logs and discovered that the culprit was actually the 'mod_sec= urity' module. It was reporting 'ModSecurity: Request body (Content-Length)= is larger than the configured limit (131072)'. Upon examining the 'mod_security.conf' configuration file, I discovered tha= t the value 'SecRequestBodyInMemoryLimit' was indeed set to the default 131= 072 bytes (128 KB). I commented out this line and the problem disappeared! = I suspect it will now allow file sizes up to the 1GB hard limit. There is another parameter 'SecResponseBodyLimit' which may also need adjus= ting. This is set to 524 288 bytes (512 KB). "Warning: The information contained in this email and any attached files is confidential to BAE Systems Australia. If you are not the intended recipient, any use, disclosure or copying of this email or any attachments is expressly prohibited. If you have received this email in error, please notify us immediately. VIRUS: Every care has been taken to ensure this email and its attachments are virus free, however, any loss or damage incurred in using this email is not the sender's responsibility. It is your responsibility to ensure virus checks are completed before installing any data sent in this email to your computer." --_000_61547C9F299F644782DDC6AB44B008D8181A0EFEmwlsvexm005auba_ Content-Type: text/html; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable

After much wailing and nashing of teeth, I’ve = finally resolved this error which was preventing me adding large files to S= VN. I tried many combinations of ‘LimitReqestBody’ and ‘L= imitXMLRequestBody’ Apache directives as suggested by many Google search results without success. I belatedly checked the Apache erro= r logs and discovered that the culprit was actually the ‘mod_security= ’ module. It was reporting ‘ModSecurity: Request body (Content-= Length) is larger than the configured limit (131072)’.

 

Upon examining the ‘mod_security.conf’ c= onfiguration file, I discovered that the value ‘SecRequestBodyInMemor= yLimit’ was indeed set to the default 131072 bytes (128 KB). I commen= ted out this line and the problem disappeared! I suspect it will now allow file sizes up to the 1GB hard limit.

 

There is another parameter ‘SecResponseBodyLim= it’ which may also need adjusting. This is set to 524 288 bytes (512 = KB).

 

"Warning:
The information contained in this email and any attached files is
confidential to BAE Systems Australia. If you are not the intended
recipient, any use, disclosure or copying of this email or any
attachments is expressly prohibited.  If you have received this email<= br> in error, please notify us immediately. VIRUS: Every care has been
taken to ensure this email and its attachments are virus free,
however, any loss or damage incurred in using this email is not the
sender's responsibility.  It is your responsibility to ensure virus
checks are completed before installing any data sent in this email to
your computer."

--_000_61547C9F299F644782DDC6AB44B008D8181A0EFEmwlsvexm005auba_--