Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of jslive@gmail.com designates
 64.233.166.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        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=gNKVD3CpueSKXxFOjmTSrDiL1OJmy7h7qAIzwa8sRQSbyU1zLSQXNJtUr4E/ljvNN6OgbHi1N/fGLLO20A9J98PzZrjRgGMfIndcXIZ5jPS1MySdatT8cGb8MHn4o9DWhaMOXnf3zkOgiuyT06gk0K7RpEpYCFdCOdVGFgW5Ue8=
Message-ID: <e498c1660706140833h79baf439o457e8278d32034ab@mail.gmail.com>
Date: Thu, 14 Jun 2007 11:33:16 -0400
From: "Joshua Slive" <joshua@slive.ca>
Sender: jslive@gmail.com
To: users@httpd.apache.org
In-Reply-To: <E3B700E9-8CF1-49AB-9CCA-F54667487F6C@rcbowen.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E3B700E9-8CF1-49AB-9CCA-F54667487F6C@rcbowen.com>
Subject: Re: [users@httpd] Invalid URI in request

On 6/13/07, Rich Bowen <rbowen@rcbowen.com> wrote:
> There is a URI on my website for which I get:
>
> Invalid URI in request GET /hr/jobs HTTP/1.1
>
> every single time the URI is accessed. The URI works as desired,
> returning the document as desired, and the end-user is never aware
> that anything untoward happened.
>
> I'm curious why I'm getting this error. I see the place in the code
> where it is generated, but I'm not clear why this particular URI
> generates it and others do not.
>
> For additional background, '/hr' is a php file, and '/jobs' therefore
> is PATH_INFO data. However, this technique is used for virtually
> every document on my website, so the technique itself is unlikely to
> be at fault - at least, as far as I can tell.

Interesting. I assume that the error is being triggered for requests
from ordinary web clients?

Is your "hr" script triggering any sub-requests?

My last-ditch effort to find the cause would be to run httpd -X under
gdb and set a breakpoint at that error message. Another option would
be simply to replace r->the_request with r->uri in the error message
so that you can see what is really triggering the problem.  (That
might actually be a good patch in general; it is silly to test the
validity of one thing and then report a possibly different thing in
the error message.) My best guess is that something in your script is
causing r->uri to get rewritten to an invalid path.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> 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