> We are currenlty in a testing phase on an ASP.NET / C# project and =
have encountered the "HTTP 400 - Bad Request" error. This only happens =
for one client. =20
>=20
> Our logs only report the following:
> 2004-05-10 06:56:37 xxx.xxx.xxx.xxx - W3SVC5 FENWEBMLMS03 =
xxx.xxx.xxx.xxx 80 - - - 400 87 224 585 0 - - - - -
>=20
I would try grabbing the request somehow to find out what is causing IIS =
to return the 400 error. You can use the windows network monitor =
driver, windump, etc to do this. Alternatively I've got an ISAPI filter =
at <a style='text-decoration: underline;' href="http://www.blushingpenguin.com/RequestFilter.html" target="_blank">http://www.blushingpenguin.com/RequestFilter.html</a> (source is around =
as well) that basically spits out the entire request/response stream to =
a log file. It has a little filtering language so that you can filter =
on IP/script name/host etc if necessary.
After you've got the request data, if you can't figure out what's wrong =
from that, post it here.<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: HTTP 400 - Bad Request