Bug #11632 Updated: Bad Request on most Sites

ID: 11632 Updated by: cynic Reported By: cheapsalsa@yahoo.com Old-Status: Open Status: Bogus Bug Type: HTTP related Operating system: PHP Version: 4.0.6 Assigned To: Comments: Maybe you should read related documentation (the Apache manual would do if the HTTP RFC is too hard to congest for you). > If I requested "http://intranet" I > would get a 400 error and in the Apache log, it would say > "Invalid URI 'GET HTTP/1.0'" instead of a valid request > "GET / HTTP/1.0"I don't see And where in "http://intranet" do you request "/"? Nowhere. This is bogus. Previous Comments: --------------------------------------------------------------------------- [2001-06-28 10:55:03] cheapsalsa@yahoo.com Yes, (my intranet site address, which I use the script on, is http://intranet) If I requested "http://intranet" I would get a 400 error and in the Apache log, it would say "Invalid URI 'GET HTTP/1.0'" instead of a valid request "GET / HTTP/1.0" BUT, if I request "http://intranet/" (WITH THE END SLASH), everything works fine! --------------------------------------------------------------------------- [2001-06-27 13:43:43] sniper@php.net No, this works for me just fine. Do you get any error messages? In apache logs? --Jani --------------------------------------------------------------------------- [2001-06-25 09:34:18] cheapsalsa@yahoo.com ok...do you see what I mean? --------------------------------------------------------------------------- [2001-06-23 16:49:38] sniper@php.net reclassified. --------------------------------------------------------------------------- [2001-06-23 15:28:40] cheapsalsa@yahoo.com Whoa! I figured something out. If I request http://finance.yahoo.com (without the last slash) I get 400 errors, but with the slash (http://finance.yahoo.com/) it works fine. As does any other page on the site (http://finance.yahoo.com/index.html) I think PHP is sending "GET HTTP/1.0" because I used the script on MY site and in my error log file, it says "Invalid URI 'GET HTTP/1.0'" --------------------------------------------------------------------------- The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online. ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=11632&edit=2