That's true, it's just a normal HTTP and HTTPS proxy I have managed a workaround by forcing connections to the problem site through a different Squid proxy which works fine I'm just a little confused on what could be causing the issue The fact the same Squid version and binaries is used on both systems but one has a newer version of the OS, makes me think it's OS Rob -----Original Message----- From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] Sent: 04 October 2007 02:30 To: Henrik Nordstrom Cc: Amos Jeffries; Robert French; squid-users@xxxxxxxxxxxxxxx Subject: Re: Squid 2.6-STABLE16 problems accessing HTTPS site with certificate > On ons, 2007-10-03 at 15:57 +1300, Amos Jeffries wrote: > >> The visible hostname must match the one inside the certificate or the >> certificate will be seen as invalid. hostname is set either in the OS >> configuration /etc/hostname, or overridden in squid.conf with >> visible_hostname. > > Hmm.. thought this was a normal proxy setup, not an https:// > accelerator / reverse-proxy. > Doh!, just got twisted around by some SSL-accel tests here while reading those email. Amos Registered in England & Wales under number 4586709 Renesas Technology Europe Ltd Dukes Meadow Millboard Road, Bourne End Buckinghamshire SL8 5FH UK
