--Wait a minute! What is an Error 400?--
According to Microsoft:
When a GET request
is submitted to a Web server
configured with Custom Error pages, the Web server
sends the following error message to the client
browser:
HTTP/1.1 Error 400 - Bad Request
This behavior is expected when the GET request itself cannot be parsed because of some kind of packet corruption. If you send a bad request to the IIS Webserver, the Custom Errors functionality is not invoked, which causes the"HTTP/1.1 Error 400 - Bad Request" error message.
If the contents of a GET request are corrupt, then the server is unable to determine the URL or the host to which the GET request should be sent. IIS is unable to retrieve the host information from the GET request packet in order to look up the meta data for the custom error. This is by design. Errors that result from severely corrupted GET requests are not customizable.
To more completely determine what may be occurring, obtain a network capture of the communication packets between the client receiving the error and the Webserver itself. Use the Microsoft Network Monitor utility to capture network packets for analysis.
O.K.
Now that we have that out of the
way...
Whatever it means to Microsoft, what a
Error 400 means to you is
that you didn't end up where you were trying to go
(/400.shtml).
So, let's try to get you there!
Navigate to:
Hopefully, you will find what you were looking for in the above list.
If you continue to receive this message, please contact the webpage admin:
*
* Please indicate the exact URLs for the page you navigated from and the page you were trying to reach.