Hi,
that solves my problems! There is no loop when wrong login parameters
are used.
Thanks a lot!
Can this mechanism be used to enforce a logout? My web site should have
a "logout/new login" link. When this link is activated, the browser
should ask for new login credentials.
Heiko
> The previous
> Yes, it is automatically sent by the component.
> However, after a little test with Firefox, and passing an invalid password,
> I see an infinite loop. Firefox infinitely retries to login with the
> wrong password. This repeats with the webserver demo easily.
>
The same happens here with IE8
>
> Do you have any proxy configures for your browser?
>
No.
--
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
>> The main problem is the following: If the user (of the browser) puts
>> in a wrong password the connection is refused. Now the user opens
>> (refresh) the page again and the browser sends the rejected digest
>> information again automatically so the login fails again.
>> Is there really no solu
>> Hi,
>>
>> I am using THttpServer with digest authentication and it works well.
>> What I need is a logout, so the user (browser) needs a new login.
>>
>
> It's IMO not possible to force the browser to display a login dialog.
> Currently the HTTP server uses a hardcoded nonce-lifetime of
Hi,
I am using THttpServer with digest authentication and it works well.
What I need is a logout, so the user (browser) needs a new login. As
long I don't close the browser the same digest information is sent by
the browser and authentication is successful.
Is there a way to force the browser to s
