I tested this out and I'm getting the same thing here. In order to see this one, you must have your browser proxy setting <Advanced> set to send Secured to the proxy along with everything else. Then you need to be blocked on a https:// request. (I realize now that I have seen this before!)
As has been mentioned, the http:// request is blocked and returns the proper redirect page. The https:// request returns a squid error page: The requested URL could not be retrieved ------------------------------------------ While trying to retrieve the URL: http:443 The following error was encountered: Unable to determine IP address from host name for http The dnsserver returned: Name Error: The domain name does not exist. -------------------------- On the http:// request, Squid logs: TCP_MISS/403 2802 GET http://www.megaproxy.com/ rick DIRECT/192.168.44.1 text/html squidGuard logs: http://www.megaproxy.com/ 192.168.44.3/- rick GET and the response sent from sg to squid is: http://192.168.44.1/cgi-bin/squidGuard.cgi?clientaddr=192.168.44.3 \ &clientname=&clientuser=rick&clientgroup=parents&targetgroup=proxy \ &url=http://www.megaproxy.com/ 192.168.44.3/- rick GET On the https:// request, Squid logs: TCP_MISS/404 0 CONNECT www.megaproxy.com:443 rick DIRECT/- - squidGuard logs: www.megaproxy.com:443 192.168.44.3/- rick CONNECT and the response sent from sg to squid is: http://192.168.44.1/cgi-bin/squidGuard.cgi?clientaddr=192.168.44.3 \ &clientname=&clientuser=rick&clientgroup=parents&targetgroup=proxy \ &url=www.megaproxy.com:443 192.168.44.3/- rick CONNECT Then instead of fetching the http://192.168.44.1 redirect page, Squid attempts to fetch http:443. I may be interpreting the data incorrectly, but it looks like squid is screwing this up. Would someone else check this out, please? I'm running: RH 7.1 squidGuard 1.20 IE 6.0.2600 Squid 2.4 STABLE6 Thanks. Rick Matthews > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Martin, Neil > Sent: Monday, August 19, 2002 10:32 AM > To: Heinz Ahrens > Cc: [EMAIL PROTECTED] > Subject: RE: problem redirector and https > > > please could you email a copy of your squidguard.conf > > Thanks > > - Neil. > > > -----Original Message----- > From: Heinz Ahrens [mailto:[EMAIL PROTECTED]] > Sent: 19 August 2002 14:06 > To: [EMAIL PROTECTED] > Subject: problem redirector and https > > > Hallo squidGuard-user, > > i use squidGuard and it works great. My only problem is an old problem > with > squidGuard but i can not find an answer. Now i wrote my problem again: > > A user can not use the adress www.megaproxy.com and with http the > redirector > redirects to: > > http://127.0.0.1./cgi-bin/blocked.pl? ...... and all is ok. (localhost > because squidGuard > and apache on the same server) > > If the user wants to get https://www.megaproxy.com squidGuard blocks the > address and that is ok. > > But he redirects to: > > http://http:443/... > > I do not want to build a SSL-webserver named http to solve the problem. > > Please help me. Are there people who solved the problem. Why is the > redirect to > http:443 ??? > > I use SquidGuard: 1.1.3 Sleepycat Software: Berkeley DB 2.7.7: > (08/20/99) > > Because of using AIX-UNIX i can not update to 1.2.0. because of Berkely > DB > (i tested a lot of them without success). > > Perhaps someone can send me a patch for 1.1.3 or the name of the > sourcefile i must edit > .... I think it is a simple programming error. > > Greeting from Germany > > Heinz Ahrens > > > > > > > _____________________________________________________________________ > > Disclaimer > > This email and any files transmitted with it, is confidential and > intended solely for the use of the individual to whom it was addressed. > > Unipath monitors emails to ensure its' systems operate effectively and > to minimise the risk of viruses. Whilst it has taken reasonable steps > to scan this email, it does not accept liability for any virus that may > be contained in it. > > > _____________________________________________________________________ > >
