|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
|
|
#1
February 18th, 2002, 10:12 AM
|
|||
|
|||
|
Bad request issue
I have a couple of sites on my server that are telling me that their web sites go down for a few minutes periodically throughout the day. During these times any request to access the sites result in a code 400 'bad request' response. Any ideas on what could be the cause of this?
|
|
#2
February 18th, 2002, 01:01 PM
|
|||
|
|||
|
This error, 400 bad request, means that a request for a URL has been made but the server is not configured or capable of responding to it. This might be the case for URLs which are handed-off to a servlet engine, where no default document or servlet is configured.
|
|
#4
February 19th, 2002, 11:43 PM
|
|||
|
|||
|
Overload would send 5XX respond code. 400 is a client-side issue. It's like asking for something that the server can't understand or not supported. Like sending HTTP/1.1 but without additional HTTP header that is required for the server to understand what you are asking for.
|
|
| Viewing: Dev Shed Forums > System Administration > Apache Development > Bad request issue |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
