Re: [twsocket] Webserver AUTH keep-alive
> This is bad design IMO. OK, changed, at least it works, so I guess it's not wrong. --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html - Original Message - From: "Fastream Technologies" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Thursday, September 07, 2006 4:40 PM Subject: Re: [twsocket] Webserver AUTH keep-alive > - Original Message - > From: "Arno Garrels" <[EMAIL PROTECTED]> > To: "ICS support mailing" > Sent: Thursday, September 07, 2006 5:36 PM > Subject: Re: [twsocket] Webserver AUTH keep-alive > > > : 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? > > We are overriding methods in C++. > > : Default HTTP/1.1 is keep-alive, Default HTTP/1.0 is closing the > connection. > > Yes. > > : 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. > > This is bad design IMO. If the latency is too high then the client would > face long connection establishment time twice. > > Regards, > > SZ > > : 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" > : > 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 > > -- > 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
Re: [twsocket] Webserver AUTH keep-alive
- Original Message - From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Thursday, September 07, 2006 5:36 PM Subject: Re: [twsocket] Webserver AUTH keep-alive : 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? We are overriding methods in C++. : Default HTTP/1.1 is keep-alive, Default HTTP/1.0 is closing the connection. Yes. : 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. This is bad design IMO. If the latency is too high then the client would face long connection establishment time twice. Regards, SZ : 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" : > 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 -- 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
Re: [twsocket] Webserver AUTH keep-alive
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" > 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
Re: [twsocket] Webserver AUTH keep-alive
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. Regards, SZ - Original Message - From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" 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
[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
