RE: [SA-list] Problem with URL check after upgrade to 5.1

[Dirk Bulinckx]

The code was changed yes. I know that SA works fine with "other" sites that need basic authentication. The fact that IE/firefox works fine doesn't mean that the response from the server is RFC compliant, and my feeling about this is that the response from the server (were it says that authentication is needed) is NOT fully RFC compliant.  But to be sure we will need to see the network trace and maybe that the developper of the URL check (we're using an "off-the-shelf" component for this) is willing to make changes to his component.   Dirk.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Klein Sent: Sunday, January 29, 2006 6:18 AM To: salive@woodstone.nu Subject: RE: [SA-list] Problem with URL check after upgrade to 5.1 Dirk,   I will try to get a sniffer trace for you. By the way, I am able to access the HTTP interface with either IE or firefox after entering username/password. Also, SAlive does not seem to have a problem when I do URL checks for other devices which require authentication. Has the code changed since the previous version?     MIke     -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Friday, January 27, 2006 6:53 PM To: salive@woodstone.nu Subject: RE: [SA-list] Problem with URL check after update to 5.1   From the logging you would expect SA to send a next frame with the usename/password, which SA isn't doing. The only reason I can see for that is that within the response frame (with the 401) there is an error. Do you have a sniffer (netmon or ethereal)?  If so can you make a network trace of SA doing the check and one of IE (or other browser) making a connection?  And send me those 2 traces (off list)   Dirk.