>-----Original Message-----
>Just a thought
>
>Under web service extensions in the IIS management
console
>
>Have you allowed ISAPI extensions. In 2003/IIS6 unknown
ISAPI extensions
>are redirected to a 404 page in the same way that they
were sent by the IIS
>lockdown tool in IIS 5/5.1
>
>Barry
>"Sofia Katchi" <anonymous@discussions.microsoft.com>
wrote in message
>news:097c01c4ad53$223fe4c0$a501280a@phx.gbl...
>> No, all it tells me is 400 bad request. No details.
>>
>> Sofia
>>
>>
>> >-----Original Message-----
>> >Hmm - anything in the httperr.log file on the
webserver?
>> >
>> >Cheers
>> >Ken
>> >
>> >
>> >"Sofia Katchi" <skatchi@accesssciences.com> wrote in
>> message
>> >news:031501c4acbf$33aeef10$a501280a@phx.gbl...
>> >>I have an ISAPI DLL that runs fine under IIS 5 / 5.1.
>> >> Recently bumped up to IIS 6 and now I am getting
>> >> intermittent 400 "Bad Request" errors. The client
>> >> performs web requests through XMLHTTP only. I've
tried
>> >> to connect with the client on 2000 and 2003 and get
the
>> >> same problem. After about 5-6 web requests (HTTP
GET
>> in
>> >> all cases) I'll come back with a 400. I assume that
>> >> XMLHTTP is sending RFC 2616 compliant HTML (using
CRLF
>> >> instead of just CR) but I don't know how I can
>> determine
>> >> this categorically. Either way, if it wasn't
sending
>> >> good HTML then it should always fail, not fail
>> >> intermittently.
>> >>
>> >> What is happening is the client EXE is caching a
number
>> >> of tables from the server during the client's start
up
>> >> process. The HTML requests are coming in rapid
>> >> succession from the same client. Again this server
>> works
>> >> fine on IIS 5 / 5.1 (Win 2000, XP and XP SP2).
>> >>
>> >> The ISAPI is runing in IIS 5 compatibility mode
>> in "Low"
>> >> isolation mode (same problem occurs in "Medium"
mode).
>> >>
>> >
>> >
>> >.
>> >
>
>
>.