There is a URI on my website for which I get: Invalid URI in request GET /hr/jobs HTTP/1.1every 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.
Any insight or suggestions appreciated.httpd 2.2.3 (yes, I know, I of all people should upgrade) on SuSE - but from source, not from package. I do not see this behavior on a 2.2.0 installation on a dev/testing machine. Will upgrade that one and see if that changes anything.
-- If you miss this moment You miss your life --------------------------------------------------------------------- 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@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|