[squid-users] Re: Trouble between Squid and SSL proxied host

Amos Jeffries-2 wrote:
>
> Close, there are some problems:
>
> https_port still needs accel and maybe vhost options to be a real
> accelerator.
>
> always_direct prevents the cache_peer config ever being used.
>
> Is the public DNS that clients are connecting to xxxxx.appspot.com or
> secure.xxxxx.com?
>
> You may need to add the forcedomain=xxxxx.appspot.com option to
> cache_peer and remove the always_direct.
>
> Amos
>

Thanks very much Amos.

The public clients are connecting to secure.xxxxx.com, and then squid is
proxying the request to xxxxx.appspot.com.

My understanding that to use vhost or accel with https_port, you needed a
wildcard SSL cert, which I don't have. Is that right?

I'm not sure what you mean here: always_direct prevents the cache_peer
config ever being used.

Thanks again! :)

-- 
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Trouble-between-Squid-and-SSL-proxied-host-tp2539814p2541528.html
Sent from the Squid - Users mailing list archive at Nabble.com.