Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 996AE18E06 for ; Fri, 24 Jul 2015 17:22:30 +0000 (UTC) Received: (qmail 91464 invoked by uid 500); 24 Jul 2015 17:22:27 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 91425 invoked by uid 500); 24 Jul 2015 17:22:27 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 91410 invoked by uid 99); 24 Jul 2015 17:22:27 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jul 2015 17:22:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id AAB10D75E9 for ; Fri, 24 Jul 2015 17:22:26 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.001 X-Spam-Level: *** X-Spam-Status: No, score=3.001 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id D0TmmXhhONCN for ; Fri, 24 Jul 2015 17:22:11 +0000 (UTC) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id AEF0020E8F for ; Fri, 24 Jul 2015 17:22:10 +0000 (UTC) Received: by wicmv11 with SMTP id mv11so72874731wic.0 for ; Fri, 24 Jul 2015 10:22:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=06WZuUXdLc0O2igpF4GQIPyQprGu8S5DSduW0o54I6A=; b=lDK7S9pkWeQ0vBsPRJOtC/h2KxnGNXeW9hEBeoqW4RdTyhOJ/Z0FuKpXhADgGi2o5m /tQxmq+T1elsl2l1YlmM/lnfhnmrvEfUNxpnneZ8lbwnHCDCUMvbA9DZh7frRC92TAt9 epy1oPhzMsCTpRLDWYJgHlpVqoK3LaMwAHOMYH7iC2ahMA0Ite0XwjIK/pd0SMFV9Ezj Wz//FhNA9XMxeiMpqauKsNbRMoYZFRjmvtVEqeKfoHLRDoqhhcKkheHJS5J4FJ4uzcPk gXgDEfYco/hnu5OUVVkBrue3am1lsuh34yWiaY6z1/QkyBXoRRMXgmgA8FfRfwuX0Rxl c6Ig== X-Gm-Message-State: ALoCoQl8s8/rqyiMkUOGbXSfzBc/NbzKdQdhUXQTURVzibtJqo6h4pL8s02iopgSetvZ6j89FgDS MIME-Version: 1.0 X-Received: by 10.180.109.136 with SMTP id hs8mr9396800wib.73.1437758530390; Fri, 24 Jul 2015 10:22:10 -0700 (PDT) Received: by 10.194.61.165 with HTTP; Fri, 24 Jul 2015 10:22:10 -0700 (PDT) In-Reply-To: References: Date: Fri, 24 Jul 2015 13:22:10 -0400 Message-ID: From: "Cohen, Laurence" To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=e89a8f2345577a281e051ba23eb9 Subject: [users@httpd] Re: Request Entity Too Large --e89a8f2345577a281e051ba23eb9 Content-Type: text/plain; charset=UTF-8 It seems that the problem I'm having started when we went to mod_nss from mod_ssl. In ssl.conf we were able to set the sslrenegbuffersize to a high number. I can't seem to find an equivalent to the parameter that will work in any of our conf files. The httpd.conf is including rewrite.conf and nss.conf, but if I put the sslrenegbuffersize in any of these files and restart httpd, it doesn't start up. Would anyone know what the equivalent parameter is in nss.conf, or the other conf files that we are using? Thanks, Larry Cohen On Thu, Jul 23, 2015 at 5:04 PM, Cohen, Laurence wrote: > Hi everyone, > > We are suddenly having the following problem on several of our servers, > and I have not been able to find a solution on the internet that has > resolved it. Our configuration is the following. > > Apache httpd 2.2.3 running on RHEL5 > Tomcat 7, also running on RHEL5 > > When we try to upload a file bigger than a few megabytes, we get the > following error: > > The requested resource > /dse/submissions/100103040/add_file > does not allow request data with POST requests, or the amount of data > provided in the request exceeds the capacity limit > > I've tried to figure out what the maximum size file is, but the problem > will occur on a file, and then we try the same file a few minutes later and > it works. > > I tried setting LimitRequestBody to 0, which I believe is the default > anyway, but it had no effect either way. > > If anyone has any ideas, please let me know. > > Thanks, > > Larry Cohen > > > -- [image: www.novetta.com] Larry Cohen System Administrator 12021 Sunset Hills Road, Suite 400 Reston, VA 20190 Email lcohen@novetta.com Office 703-885-1064 --e89a8f2345577a281e051ba23eb9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It seems that the problem I'm having st= arted when we went to mod_nss from mod_ssl.=C2=A0 In ssl.conf we were able = to set the sslrenegbuffersize to a high number.=C2=A0 I can't seem to f= ind an equivalent to the parameter that will work in any of our conf files.= =C2=A0 The httpd.conf is including rewrite.conf and nss.conf, but if I put = the sslrenegbuffersize in any of these files and restart httpd, it doesn= 9;t start up.

Would anyone know what the equivalent parameter = is in nss.conf, or the other conf files that we are using?

Tha= nks,

Larry Cohen

On Thu, Jul 23, 2015 at 5:04 PM, Cohen, Laurence <l= cohen@novetta.com> wrote:
<= div dir=3D"ltr">Hi everyone,

We are suddenly having the = following problem on several of our servers, and I have not been able to fi= nd a solution on the internet that has resolved it.=C2=A0 Our configuration= is the following.

Apache httpd 2.2.3 running on R= HEL5
Tomcat 7, also running on RHEL5

Whe= n we try to upload a file bigger than a few megabytes, we get the following= error:

The requested resource
/dse/submissions= /100103040/add_file
does not allow request data with POST requests, or = the amount of data provided in the request exceeds the capacity limit
=

I've tried to figure out what the maximum size file= is, but the problem will occur on a file, and then we try the same file a = few minutes later and it works.

I tried setting=C2= =A0LimitRequestBody to 0, which I believe is the default anyway, but it had= no effect either way.

If anyone has any ideas, pl= ease let me know.

Thanks,

Larry Cohen


<= /span>




--

3D"www.novetta.com"

Larry Cohen

System = Administrator


12021 Sunset Hills Road, Suite 400

Reston, VA 20190

Email =C2=A0lcohen@novetta.com

Office =C2=A0703-885-1064

--e89a8f2345577a281e051ba23eb9--