On Dec 17, 2007 5:50 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > Amos Jeffries wrote: > >> Dear All, > >> I would like to redirect http://gmail.com to https://gmail.com > >> because http://gmail.com was banned by our ISP > >> But they allow https://gmail.com > >> User only know http://gmail.com but when they visit, it was banned. > >> Almost the time, I have to go to user and say to use https://gmail.com .. > >> > >> Any suggestions is appirciated > >> > > > > Two approaches: > > > > 1) automatic teaching clue-by-4 stick for your users: > > > > acl badGmail dstdomain gmail.com > > acl HTTP proto HTTP > > deny_info http://yourhostname/gmail_is_broken.html badGmail > > http_access deny HTTP badGmail > > > > > > 2) leave the peons ignorant and MAKE it work: > > > > acl badGmail dstdomain gmail.com > > acl HTTP proto HTTP > > > > cache_peer gmail.com 443 0 no-query originserver > > Sorry I forgot to add there may be ssl* options needed for SSL traffic > between squid and the gmail HTTPS server. > > > > cache_peer_access gmail.com allow badGmail > > cache_peer_access gmail.com deny !badGmail > > never_direct deny HTTP badGmail > > > Thanks you very much Mr. Amos. It really work for me. Here is good configuration ###### GMail Redirection ###### acl bad_gmail dstdomain gmail.com acl HTTP proto HTTP cache_peer gmail.com parent 443 0 no-query cache_peer_access gmail.com allow bad_gmail cache_peer_access gmail.com deny !bad_gmail never_direct deny HTTP bad_gmail ############################## > Amos >
