Re: [squid-users] Reverse proxy SSL on non-standard port

Many thanks for your help. I'm trying to follow your
advice by using the myport and cache_peer_access
directives, as seen in the configuration below.
However, with this configuration my clients receive
the following error message:

While trying to retrieve the URL:
http://webmail.yyy.com:0/

The URL entered was https://webmail.yyy.com/

I guess I'm not following how the redirection is
working. Here's the config:

httpd_accel_single_host off
httpd_accel_with_proxy on
httpd_accel_uses_host_header on
redirect_rewrites_host_header on
                                                      
                         
httpd_accel_host webmail.sfbr.org
              httpd_accel_port 0
https_port 443 cert=/etc/squid/webmail.pem
https_port 444 cert=/etc/squid/webmail.pem

                                                      
                         
cache_peer webmail.yyy.com parent 443 0 proxy-only
cache_peer webmail.yyy.com parent 444 0 proxy-only
                                                      
                         
acl web443 myport 443
acl web444 myport 444
cache_peer_access webmail.yyy.com allow web443
cache_peer_access webmail.yyy.com allow web444

Thanks,

-tjh

--- Henrik Nordstrom <hno@squid-cache.org> wrote:

> With the above you can use the myport acl in
> combination with
> cache_peer_access to select which peer (web server)
> the requests should be
> sent to, but to be honest you are bordering on the
> limits of what the
> Squid-2.5 accelerator function can cope with.
>
> What should work for your specific situation is to
> httpd_accel_host webmail.yyy.com
> httpd_accel_port 0
> https_port 443 cert=/etc/squid/webmail.pem
> https_port 444 cert=/etc/squid/webmail.pem
>
>

                
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
Received on Sun Oct 03 2004 - 16:19:48 MDT