Hot answers tagged 400
Just to expand on MrTuttle's answer, the 400 errors I've investigated in the wild are typically someone trying (unsuccessfully) to exploit your webserver, typically because they haven't noticed that you're not running a vulnerable version, or they just don't care. A fair proportion of the 404 errors I get on my sites are in the same boat -- attempts to ...
You could define a custom ErrorDocument for the 400 Errors like so: ErrorDocument 400 /cgi-bin/handle400.cgi and then have that cgi (or php or servlet or whatever) do the header rewriting and location redirecting. EDIT: because of Jacek's answer I just tested above solution to confirm it works on Apache 2.2. My Server Config: ScriptAlias /cgi-bin/ ...
It didn't send an HTTP version string (HTTP/1.1 or HTTP/1.0), that client is not speaking correct HTTP. It should most certainly get a 400 Bad Request response. See RFC 2616: The request could not be understood by the server due to malformed syntax.
I was looking in the wrong place. For Errors, you need to look in systemroot\System32\LogFiles\HTTPERR. http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/bcabdcfb-2421-4eab-b5fb-777c791daaa9.mspx?mfr=true
check this articles KB810957 which explains the cause of the issue and UploadReadAheadSize is the solution for the same. Let me know if that helps.
Only top voted, non community-wiki answers of a minimum length are eligible