Fastream Technologies wrote: > Well, in our code, unless the client request type is close, we return > keep-alive if it is NOT HTTP/1.0 and 1.1.
So, are you using your own copy with individual changes? Default HTTP/1.1 is keep-alive, Default HTTP/1.0 is closing the connection. I've done the following: If a client sends a request for a protected page and has not yet the Authorization header it will be sent header "Connection: close" in HTTP/1.1. Otherwise, if not NTLM, the requested type is used. --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > > Regards, > > SZ > > ----- Original Message ----- > From: "Arno Garrels" <[EMAIL PROTECTED]> > To: "ICS support mailing" <twsocket@elists.org> > Sent: Thursday, September 07, 2006 4:40 PM > Subject: [twsocket] Webserver AUTH keep-alive > > >> Hi, >> >> Current code doesn't handle keep-alive in the >> 401 response. >> >> What are the recommended keep-alive headers with >> Basic as well as Digest? >> >> M$ IIS sends always Connection: close in the first >> 401 header. >> >> Currently I do the same. >> >> Any veto? >> >> --- >> Arno Garrels [TeamICS] >> http://www.overbyte.be/eng/overbyte/teamics.html >> >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://www.elists.org/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
