The first is denied by your configuration requiring authentication for the connection to proceed.
The second definitely smells like a browser bug in how it handles access denials when trying to reach https:// URLs... Squid should not ever ever see the url PATH of https:// requests when used as a proxy, and if it does your browser is very broken. What browser are you using? And what authentication scheme? (basic or ntlm?) Regards Henrik tis 2003-02-11 klockan 10.41 skrev Deac Nkisetlein: > Dear listmembers, > > after upgrading from 2.4S6 to 2.5S1 on a solaris 2.8 box with 512mb RAM, > basic-smb_auth and squidguard I experience the following error: > > Everything works fine, as long as user requesting http URL's. > > If a https resource is requested, the error: "URL could not be loaded" > is displayed. Theres no error on the requested sites, they working fine. > Lets assume, the URL would be: https://www.foo.com/bar/bla/cgi > > Access log shows up the following: > > > xx.xx.xx.xx - - [11/Feb/2003:10:28:09 +0100] "CONNECT www.foo.com:443 > HTTP/1.0" 407 1472 TCP_DENIED:NONE > xx.xx.xx.xx - - [11/Feb/2003:10:28:11 +0100] "GET /bar/bla/cgi HTTP/0.0" 400 > 1627 NONE:NONE > > As you can see, there are two (!) requests made. The first one for the host > and a > second one for the requested path. Mutilated in that way, these requests are > failing. > > An interesting thing is that if I hit reload on this error, the pages load > very fine. > > Any help is greatly appreciated!! > > Regards. -- Henrik Nordstrom <[EMAIL PROTECTED]> MARA Systems AB, Sweden
