Re: [squid-users] cache_peer causes 'https proxy request speaking HTTP to HTTPS port' error

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Thu, 26 May 2011 23:56:21 +1200

On 26/05/11 23:46, Stephan Hügel wrote:
>> Does "squid -k parse" bring up any warnings?
>
> No, none. I can connect successfully to the peer address using openssl
> and the cert I've specified, and a HTTP 1.1 GET works, so the cert
> seems to be OK.
>

Um, the failures are on CONNECT requests? That could be the bug we only
just fixed a few days ago. Where Squid re-wraps the CONNECT headers
around it before passing to any peer (even SSL ones).

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.12
   Beta testers wanted for 3.2.0.7 and 3.1.12.1
Received on Thu May 26 2011 - 11:56:27 MDT

This archive was generated by hypermail 2.2.0 : Thu May 26 2011 - 12:00:03 MDT