Colin
Error 502 is "Bad Gateway" meaning a proxy had trouble connecting to an
upstream device. This could be a fault on the BlueCoat, or it could be a
fault on a reverse proxy at the remote site, if Terabithia uses reverse
proxies. I don't think it's your Squid proxy. But perhaps try running
wget/curl on your squid proxy and setting https_proxy to 192.168.0.10. If
the problem persists, this will not only rule out the Squid proxy, but the
web page returned may give more detail about the cause. As it's related to
https vs http, I'm guessing the BlueCoat is having a problem with
Terabithia's certificate.
Also, try running wget on your content mirror to fetch something via https
known to be working like https://www.google.com/.
Cheers
Jeremy
On Fri, 7 Jun 2019 at 09:57, Colin Coe <user-5b250cd7a540@xymon.invalid> wrote:
Hi
I'm trying to sync the Xymon repos on terabithia.org locally.
I had this working when http was accepted but since its gone https, I just
see 502 messages in my squid logs:
1559864923.715 585 192.168.0.90 TCP_TUNNEL/502 0 CONNECT
terabithia.org:443 - FIRSTUP_PARENT/192.168.0.10 -
I've tried wget and curl with the same result:
https_proxy=https://192.168.0.12:3128 wget -r --no-parent
--no-check-certificate https://terabithia.org/rpms/xymon/el6/
192.168.0.90 is the local content mirror (RHEL7, fully patched)
192.168.0.10 is our upstream proxy (BlueCoat, managed by another group)
192.168.0.12 is our local proxy (Squid on RHEL7, fully patched)
(Not our real IP's)
Any ideas?
Thanks