Re: [squid-users] ssl connections

Henrik Nordstrom wrote:

>On Mon, 29 Mar 2004, Emilio Casbas wrote:
>
>
>
>>We've 2 foundrys in each level for balancing load and we have seen the
>>"SSL session ID
>>switching" parameter, but this is for TCP 443 port , wich is the
>>ServerIron's ability to connect
>>a client to the same real server to wich it had previously established
>>an SSL connection.
>>
>>
>
>This shuold not at all be related to user sessions, just performance.
>
>
>
>>Is there more people experimenting troubles with ssl connections in an
>>environment with proxis hierarchi and load balancing?.
>>
>>
>
>Almost all problems I have heard of comes from the user not always coming
>from the same source IP address when going via a mesh of proxies. Most I
>have heard of solves this by setting up a dedicated/deterministic
>forwarding path for CONNECT requests. These can not be cached so it is not
>much value in having all the dynamic properties of a cache mesh to
>increase hit ratio..
>
>Regards
>Henrik
>
>
>
Ok, then to do a forwarding path is it possible:

1. Via "cache_peer_access "
2. Via "acl name method"
3. any more?

Wich is the best method to implement the forwarding path only for
connect requests?

Thanks
Emilio C.