Secure Web Access Using Non-standard Ports

I have a problem with one site that uses the standard https port for the
initial connection and then switches ports to access specific web data.

There is no problem when the user is directly connected to the Internet or
when the user is behind a firewall like FireWall-1. However, the site is
not accessible when the request is passed through Squid.

Is there anything more needed to be changed than to add the specific ports
to the SSL acl? Is there a way to have two conditions met? The specific
web site and the port?

Merton Campbell Crockett
Received on Mon Mar 27 2000 - 13:00:38 MST