Hi Pierre,
IIS is doing the right thing here. Per RFC2616 (the HTTP/1.1 spec), the
absence of a Connection header means that the connection will be kept alive.
If the IIS server were going to close the connection, then it would send a
"Connection: close" header in the response.
Note that HTTP/1.0 (RFC1945 if I remember right) is exactly the opposite.
The absence of a Connection header indicates that the server will close the
connection. In this case, IIS would be setting a "Connection: keep-alive"
header if it is going to keep the connection open.
Also note that the connection response headers are completely managed by
IIS. You should never add a connection header to your response, or you
introduce the possibility of breaking the response.
Thank you,
-Wade A. Hilmo,
-Microsoft
"Pierre Bru" <Pierre.Bru.TakeThisOut@spotimage.fr> wrote in message
news:#UUHJ200GHA.4016@TK2MSFTNGP02.phx.gbl...
> hi,
>
> I have ASP scripts on a Win2K3/II6 server with persistent connections
> activated.
>
> when a browser (IE6, FF1.5) sends a HTTP/1.1 request containing a
> "Connection: Keep-Alive", the server answers with a 200 answer but with
> neither "Connection: Keep-Alive" nor "Connection: Close" header (should
> be a "Connection: Close" as the answer is complete)
>
> is it to the ASP script to add the Connection header ? or is there some
> setting in IIS ?
>
> TIA,
> Pierre. >> Stay informed about: IIS6 not sending "Connection" header