Re: [twsocket] AuthType for THttpServer...
Arno Garrels wrote: > zayin wrote: >> Hi Arno, >> >> Thanks for the response. >> >>> Have a look at the OverbyteIcsWebServ demo it provides Basic, Digest >>> and NTLM examples and one for all three authentication types. >> >> It produces the same result with Safari. The source file is "Mar 04, >> 2006 V1.5". > > You use a very old ICS version. Please update to latest ICSv7, > available here: http://wiki.overbyte.be/wiki/index.php/ICS_Download > > >> >> In the example, if the client URL is configured correctly the auth >> will be set to the data contained in the URL. If the URL is '/' which >> is the case when the user is browsing to an IP address, the auth >> configured on the THttpServer component is used. And that is the rub. >> I need to leave the property as basic auth but Safari only accepts >> digest. >> >> So, it appears I need have users of Safari use a special URL so I can >> change the auth to digest. >> >> Sound right? > > Don't think so, the server sends the supported auth.-types with the > 407-response to the client (as header lines one for each supported > auth.-type). The client picks the one it likes, that works very well > with current demo. Correction: It sends the authorization headers with the 401 response, 407 is sent by proxies only (I was recently too busy with HTTP proxies :) See method THttpConnection.Answer401. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] AuthType for THttpServer...
zayin wrote: > Hi Arno, > > Thanks for the response. > >> Have a look at the OverbyteIcsWebServ demo it provides Basic, Digest >> and NTLM examples and one for all three authentication types. > > It produces the same result with Safari. The source file is "Mar 04, > 2006 V1.5". You use a very old ICS version. Please update to latest ICSv7, available here: http://wiki.overbyte.be/wiki/index.php/ICS_Download > > In the example, if the client URL is configured correctly the auth > will be set to the data contained in the URL. If the URL is '/' which > is the case when the user is browsing to an IP address, the auth > configured on the THttpServer component is used. And that is the rub. > I need to leave the property as basic auth but Safari only accepts > digest. > > So, it appears I need have users of Safari use a special URL so I can > change the auth to digest. > > Sound right? Don't think so, the server sends the supported auth.-types with the 407-response to the client (as header lines one for each supported auth.-type). The client picks the one it likes, that works very well with current demo. -- Arno Garrels > > Ciao, > > Mark > > > > > > > > > -Original Message- > From: zayin [mailto:za...@pdq.net] > Sent: Saturday, March 12, 2011 9:37 AM > To: 'twsocket@elists.org' > Subject: AuthType for THttpServer... > > Hello, > > I have been using AuthType set to atBasic to support all comers. > > I have a new user that is using Safari and it appears to only use > atDigest. I have not found a setting in Safari to allow basic mode. I > tried sending the user name or user name and password from Safari in > the url but that did not work. > > I do not see in THttpServer how to support both. > > Ideas? > > Thanks, > > Mark -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] AuthType for THttpServer...
Hi Arno, Thanks for the response. > Have a look at the OverbyteIcsWebServ demo it provides Basic, Digest > and NTLM examples and one for all three authentication types. It produces the same result with Safari. The source file is "Mar 04, 2006 V1.5". In the example, if the client URL is configured correctly the auth will be set to the data contained in the URL. If the URL is '/' which is the case when the user is browsing to an IP address, the auth configured on the THttpServer component is used. And that is the rub. I need to leave the property as basic auth but Safari only accepts digest. So, it appears I need have users of Safari use a special URL so I can change the auth to digest. Sound right? Ciao, Mark -Original Message- From: zayin [mailto:za...@pdq.net] Sent: Saturday, March 12, 2011 9:37 AM To: 'twsocket@elists.org' Subject: AuthType for THttpServer... Hello, I have been using AuthType set to atBasic to support all comers. I have a new user that is using Safari and it appears to only use atDigest. I have not found a setting in Safari to allow basic mode. I tried sending the user name or user name and password from Safari in the url but that did not work. I do not see in THttpServer how to support both. Ideas? Thanks, Mark -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] AuthType for THttpServer...
Hello zayin, > Hello, > > I have been using AuthType set to atBasic to support all comers. > > I have a new user that is using Safari and it appears to only use > atDigest. I have not found a setting in Safari to allow basic mode. I > tried sending the user name or user name and password from Safari in > the url but that did not work. > > I do not see in THttpServer how to support both. Have a look at the OverbyteIcsWebServ demo it provides Basic, Digest and NTLM examples and one for all three authentication types. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] AuthType for THttpServer...
Hello, I have been using AuthType set to atBasic to support all comers. I have a new user that is using Safari and it appears to only use atDigest. I have not found a setting in Safari to allow basic mode. I tried sending the user name or user name and password from Safari in the url but that did not work. I do not see in THttpServer how to support both. Ideas? Thanks, Mark -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] AQTime reportingleak withDispatchMessage()usingTHttpCli
> None of the ICS components are using threads by itself. The ICS FTP server does use threads if command processing is going to take a long time, such as calculating the MD5 of a large file, but there is no message processing in those threads. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
