Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 1779 invoked from network); 25 Jul 2006 13:33:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jul 2006 13:33:13 -0000 Received: (qmail 47025 invoked by uid 500); 25 Jul 2006 13:33:01 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 47005 invoked by uid 500); 25 Jul 2006 13:33:01 -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 46994 invoked by uid 99); 25 Jul 2006 13:33:01 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 06:33:01 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jslive@gmail.com designates 66.249.92.171 as permitted sender) Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 06:33:00 -0700 Received: by ug-out-1314.google.com with SMTP id u2so346072uge for ; Tue, 25 Jul 2006 06:32:39 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=lV9eac0sHT/iSQt4+PhC7P64rqF4C3H99bkD3K7ydhZ3AETYXrsg2qL/Tez72vrDg5wBXv6d5KnjrhTRoG/vEHi8sU5oPU8VDKyMRbXeAdRxi5h5suToBufPW85ZN3gMlQgcRfgKF0NtNuKg7sDE4VcBRUamN0EdImtjZfh8LXc= Received: by 10.78.151.3 with SMTP id y3mr2300096hud; Tue, 25 Jul 2006 06:32:39 -0700 (PDT) Received: by 10.78.142.9 with HTTP; Tue, 25 Jul 2006 06:32:38 -0700 (PDT) Message-ID: Date: Tue, 25 Jul 2006 09:32:38 -0400 From: "Joshua Slive" Sender: jslive@gmail.com To: users@httpd.apache.org In-Reply-To: <9EE2AB3E13F8844AB35BF44F17268D7163FA20@Milestonee.milestone.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9EE2AB3E13F8844AB35BF44F17268D7163FA20@Milestonee.milestone.dk> X-Google-Sender-Auth: bd8c5331aeb456d7 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] referer header field too long? X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 7/25/06, Peter Posselt Vestergaard wrote: > > -----Original Message----- > > From: jslive@gmail.com [mailto:jslive@gmail.com] On Behalf Of > > Joshua Slive > > Sent: 24. juli 2006 17:30 > > To: users@httpd.apache.org > > Subject: Re: [users@httpd] referer header field too long? > > > > On 7/24/06, Peter Posselt Vestergaard wrote: > > > Hi > > > We have a number of Apache HTTP servers installed all with version > > > 2.0.54. > > > Lately we have seen a number of "400 Bad Request" in the > > error logs, and > > > after a lot of testing we have found that this happens then the > > > "Referer" HTTP header field in the request contains a URL > > that it more > > > than 200 characters long. > > > We have searched the web and apache web site without > > finding anything > > > about this. > > > Can someone confirm this and tell us how to work around it? > > We cannot > > > easily replace the servers, so we would prefer another > > solution... but > > > if no such exist we would like to know whether this has > > been corrected > > > in a later version of the Apache server? We are not > > interested in the > > > referer field, so it would be okay if Apache could just ignore it. > > > > 200 characters would be a very unusual limit. You can check > > http://httpd.apache.org/docs/2.2/mod/core.html#limitrequestfieldsize > > but I suspect the problem may be elsewhere, such as an > > intermediate proxy. > > > > Joshua. > > > Thanks for your answer. > However we have not set that setting and I am entirely sure that no > proxy is in between. We first saw the error on a customer setup, but > have been able to reproduce the problem on our local setup in which we > know that no proxy is in between. I would look for something else other than the length of the Referer. What does the apache error log say? Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org