RE: [SQU] web page not working since squidding

From: Merton Campbell Crockett <mcc@dont-contact.us>
Date: Tue, 10 Oct 2000 08:46:56 -0700 (PDT)

This is from the configuration file distributed with Squid 2.2STABLE5.

# TAG: tcp_incoming_address
# TAG: tcp_outgoing_address
# TAG: udp_incoming_address
# TAG: udp_outgoing_address
# Usage: tcp_incoming_address 10.20.30.40
# udp_outgoing_address fully.qualified.domain.name
#
# tcp_incoming_address is used for the HTTP socket which accepts
# connections from clients and other caches.
# tcp_outgoing_address is used for connections made to remote
# servers and other caches.
# udp_incoming_address is used for the ICP socket receiving packets
# from other caches.
# udp_outgoing_address is used for ICP packets sent out to other
# caches.
#
# The default behaviour is to not bind to any specific address.
#
# NOTE, udp_incoming_address and udp_outgoing_address can not
# have the same value (unless it is 0.0.0.0) since they both use
# port 3130.
#
#tcp_incoming_address 0.0.0.0
#tcp_outgoing_address 0.0.0.0
#udp_incoming_address 0.0.0.0
#udp_outgoing_address 0.0.0.0

I have squid running on firewall/bastion host and specify the IP address
of the internal interface using the incoming tags to restrict access to
internal clients and proxies.

Merton Campbell Crockett

On Tue, 10 Oct 2000, Randy Bey wrote:

> The squid.conf file in 2.2STABLE5 does not have syntax for adding inside
> only.
> I reused the squid.conf from 2.3STABLE4, except for a small change in the
> cache_dir line.
> The line
> http_port 10.1.1.1:80
> was not refused by squid when it started, but on the other hand, I got no
> listener on port 80 anywhere on the machine until I changed it to
> http_port 80
>
> What am I doing wrong?
>
> -----Original Message-----
> From: Robert Collins [mailto:robert.collins@itdomain.com.au]
> Sent: Monday, October 09, 2000 5:03 PM
> To: Randy Bey; 'Joe Cooper'
> Cc: squid-users@ircache.net
> Subject: Re: [SQU] web page not working since squidding
>
>
> squid 2.3 also allows you to listen on the inside only. use
> http_port in.si.de.ip:80
>
> Rob
>
> ----- Original Message -----
> From: Randy Bey <mailto:Randy.Bey@rivernorthsys.com>
> To: 'Joe Cooper' <mailto:joe@swelltech.com>
> Cc: 'squid-users@ircache.net' <mailto:'squid-users@ircache.net'>
> Sent: Tuesday, October 10, 2000 8:26 AM
> Subject: RE: [SQU] web page not working since squidding
>
>
>
> I have tried using the "older" version of squid, 2.2STABLE5, and it works
> with www.carsoup.com <http://www.carsoup.com> as well as various other
> scripted pages.
>
> So, is this something that was subsequently broken in 2.3STABLE4 or do I
> have a configuration issue?
> I would like to return to 2.3STABLE4 because it allows me to set up squid to
> only listen on our inside port for proxy requests. In other words, we do not
> advertise a service on port 80 (our squid http_port) to the outside world,
> only to the inside interface.
>
>
>
>

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
Received on Tue Oct 10 2000 - 09:55:30 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:55:43 MST