|Posted: 11 August 2011 at 6:06pm
Our company is running a legacy www retrieve application from 1995 that is failing after the migration. I seem to have tracked the issue down to the HEADER values being passed to the server.
When the application calls the web page normally, IIS responds with a basic 400 error. httperr.log is giving the following.
2011-08-11 20:01:33 10.10.10.14 741 10.10.10.14 80 HTTP/0.0 GET /page.htm 400 - BadRequest -
2011-08-11 20:02:11 10.10.10.14 2795 10.10.10.14 80 HTTP/0.0 GET /page.htm 400 - BadRequest -
When i call it directly through Fiddler using a crafted header, i get the same error.
IIS6 Windows 2003 Standard
GET /page.htm HTTP/V1.0
HTTP/1.1 400 Bad Request
Date: Thu, 11 Aug 2011 19:59:22 GMT
However, When I call it directly through Fiddler using a proper crafted header for HTTP/1.0, the page is retrieved and IIS responds properly. Even though all i changed was the HEADER to HTTP/1.0 and not HTTP/V1.0.
So, is it possible to use the rewriteheader option to rewrite the incoming header before IIS processes the request?