Question:
This error (HTTP 400 Bad Request) means that Internet Explorer was able to connect to the web server, but the?
2013-12-19 10:42:31 UTC
This error (HTTP 400 Bad Request) means that Internet Explorer was able to connect to the web server, but the webpage could not be found because of a problem with the address.

For more information about HTTP errors, see Help.
Four answers:
?
2013-12-19 13:11:50 UTC
can't be plainer. URL was bad. what's the question?
adaviel
2013-12-21 10:36:43 UTC
I've not seen that with a browser. But the following will get error 400 from Apache:

$telnet www.example.com 80

GET / HTTP/3.4

GET foo HTTP/1.0

others get 501 not supported, e.g.

GOO /



Normally if you ask a browser for http://www.example.com/foo it does

GET /foo HTTP/1.1 and gets a 404. IE automatically inserts the "/".



I guess you might get 400 from an active script on a webserver, where the programmer has decided to send 400 rather than the default 500-series error, or maybe trying to do WebDAV to a non-WebDAV server. But it's not normal. 400 is supposed to mean the client made an error, while 500 is if the server made an error (an active script failed, for instance). As if there was a bug in Internet Explorer (or a web proxy) causing it to generate an illegal request, not just one the server didn't understand.
Nik
2013-12-19 10:43:53 UTC
Web sites can contain sub domains subpages so although the information associated with the web site is correct he sub address doesn't make sense hence bad request it can connect to the server and the site but the site has given a bad response IE no page wrong document etc.
Dennis
2014-03-11 09:29:04 UTC
I Can't get in to my Twitter Account I got another follower It says Internet was able to connect to web server, but the webpage could not found because of a problem with the address Please fix it so I can accept my new follower!


This content was originally posted on Y! Answers, a Q&A website that shut down in 2021.
Loading...