RE: [squid-users] non-standard HTTP ports

Hi,
Do you mean that Squid refuses the connection?
If so, are those ports allowed in the Safe_ports, or similar ACL?

Regards,

Bruno Guerreiro

-----Original Message-----
From: Dav Stott [mailto:dstott@csl.gov.uk]
Sent: quinta-feira, 31 de Maio de 2001 15:13
To: squid-users@squid-cache.org
Subject: [squid-users] non-standard HTTP ports

Hi All,

I've been knocking my head against this one for a couple of days now and
am in need of some assistance.

We've just put a new firewall in which only allows HTTP through on port
80. All our users go through a squid system on port 3128, the squid box is
then allowed outside by the firewall. However, the problem arises when a
user tries to use a webserver on anything other than port 80, e.g. 8080,
2139.

What I need is to tell squid (2.4stable1) to send it's HTTP requests
onto another proxy (in the same way that the users browsers are
pointed towards squid:3128)

I've tried using tcp_outgoing_address,

"cache_peer firewall parent 80 3130 no-query"

and even tried forcing forward.c to use port 80 in it's comm_open() calls,
but always wind up with a connection refusal.

I guess this is a fairly common thing that's encountered, but as I can't
find anything obvious in the mailing list archives I figure I've just
missed something blindingly obvious.

Cheers,

Dav

-- 
--------------------------------------------------------------
Dav Stott                       Phone: +44 (0)1904 462137
Systems Development Engineer    GTN:   5129 2137
Central Science Laboratory      Fax:   +44 (0)1904 462111
Sand Hutton                     Email: d.stott@csl.gov.uk
York YO41 1LZ, UK               WWW:   http://www.csl.gov.uk/
--------------------------------------------------------------