"Alex Krawarik [MSFT]" <alexkr@o...> wrote in message 
news:evRAD3tTHHA.1208@T......
>> Further to this : IIS is behaving differently to apache. The client kills 
>> the connection (RST, not FIN), a minute after the POST request when it 
>> came back from IIS. Any idea why it does this? It would be an acceptable 
>> get-round if I could get it to do it (bump the server side timeout time 
>> to > the client side, which would mean the client would always timeout 
>> first and thus not get the opportunity to experience the problem I'm 
>> seeing).
>>
>> cheers,
>> clive
>
> I suppose thats not really a surprise. You could "time out" the client 
> immediately by setting the cache-control header to no-cache maybe?
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html

That's cache, not connection. A lot of the stuff is no-cache anyway.

If I turned off keepalive on the server, the problem would not occur - but 
I'd lose performance. Ditto "connection: close" - if I knew what the call 
immediately preceding the POST was, I could do that, but I don't.

cheers,
clive