Re: [squid-users] Squid 3.0 SSL connection

resolved.

moved the 443 higher in the conf file than the 80.

>>> Henrik Nordstrom <hno@squid-cache.org> 8/23/2004 1:05:49 PM >>>

Please keep discussion on the mailinglist thanks.

Regards
Henrik

On Mon, 23 Aug 2004, Rob O'Connor wrote:

> I am still hung up - is it possible to have the same originserver
url
> accel for both port 80 and 443? Even with the access, If I remove
the
> http accel 80 the https works, but then the http does not. and vice
> versa.
>
> Changed to:
> cache_peer 10.x.y.2 parent 80 0 no-query originserver
> cache_peer 10.x.y.135 parent 80 0 no-query originserver
> cache_peer 10.x.y.139 parent 80 0 no-query originserver
> cache_peer host.domainname parent 443 0 no-query ssl proxy-only
> originserver
>
> problem is host.domainname ip is 10.x.y.2 so it defaults back to
port
> 80
>
>
>>>> Henrik Nordstrom <hno@squid-cache.org> 8/20/2004 7:22:11 PM >>>
> On Fri, 20 Aug 2004, Rob O'Connor wrote:
>
>> cache_peer 10.x.y.2 parent 80 0 no-query originserver
>> cache_peer 10.x.y.135 parent 80 0 no-query originserver
>> cache_peer 10.x.y.139 parent 80 0 no-query originserver
>> cache_peer 10.x.y.2 parent 443 0 no-query ssl proxy-only
> originserver
>
> You have many peers defined, but I see no directives telling Squid
when
> to
> use which peer.
>
> See the cache_peer_access directive.
>
> Regards
> Henrik
>
Received on Mon Aug 23 2004 - 14:29:31 MDT