Thanks for your response. It's clear we need to get an exception for our
grid machines. Read on if you're interested in the details.
Cheers,
Peter
The problems encountered are with wget and curl. For example, Atlas have
the following usage:
https: 443, 25443, 26443
http: 80, 25880, 26080
curl -o out.tar.gz -sS --insecure https://gridui01.usatlas.bnl.gov:25443/cache/sources.1bf7d4a9-557c-4128-8c6c-5790c75d947a.tar.gz
wget --no-check-certificate https://gridui01.usatlas.bnl.gov:25443/cache/sources.1bf7d4a9-557c-4128-8c6c-5790c75d947a.tar.gz
Our campus network only allow outbound port 80 via their webcache. I
can't see a way to configure these clients to use the webcache for port
80 traffic and use a DIRECT connection for non port-80. wget can handle
this 'no_proxy' syntax but curl doesn't care about port numbers:
export no_proxy="lancs.ac.uk, lancs.pygrid, :25443, :443, :26443, :25880, :26080,"
Ho-hum.
Peter Love ([log in to unmask]) wrote:
> Hi all,
>
> Can every site please respond to this stating whether or not their site
> is encumbered with a web cache proxy server?
>
> We have this at Lancaster and it's causing ongoing problems with various
> VOs due to broken clients and their usage (wget,curl etc.).
>
> Many thanks,
> Peter
|