In v4 you could enable the use of cookies, in v5 that is always done.  BUT those are session cookies (in both cases) not cookies that are kept (on disk) over several sessions.
 
Within the answer of the server there is NO authentication request nor any cookie info.  I realy don't see what we're doing wrong.
 
If you still have a v4.x installed, then let it do a check of the exact same URL and make a network trace (netmon - ethereal) of it and then do the same with v5.  Maybe even one were we can see IE doing this.  And send me (off list) the 3 network traces.  We can then compare to see what the difference is.
 

Dirk.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Deadman, Phil
Sent: Friday, November 11, 2005 10:41 AM
To: [email protected]
Subject: RE: [SA-list] http/auth checks not working after upgrade to v5

Wasn't there something in v4 about using cookies? If this isn't basic or NTLM it must be cookie-based authentication.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
Sent: 10 November 2005 22:13
To: [email protected]
Subject: RE: [SA-list] http/auth checks not working after upgrade to v5

A password challenge page is not a real HTTP password page. 
Within a normal GET request you can only do authentication if the server send a authentication request and and authentication request is not an HTML page like the one you're seeing.
I don't see how v4 could have done authentication without an authentication request that is server based.
 

Dirk.

 


***********************************************************************************************
This E-mail and any files transmitted with it is intended for the use of the
addressee only and may contain confidential information. If you are not the
intended recipient you are hereby notified that any use or dissemination of
this communication is strictly prohibited. If you receive this transmission
in error, please notify us immediately and delete this e-mail.
The views and opinions expressed in this e-mail message are the author's own
and may not reflect the views and opinions of Signet Group plc
or any of its subsidiaries.
***********************************************************************************************

Reply via email to