Re: http_port directive and secondary IP addresses: SQUID 2.3S1segmentation fault

Eelco,

Thank's a lot.
Yes, it seems to work with a hostname instead of an IP address
in http_port directive.

I'll look at the sources asap to see it its a bug or a feature :-)

Thank's again and best regards to all "Squiders" !

Thierry A.

Eelco M Glasl wrote:

> On Tue, 22 Feb 2000, Thierry Agassis wrote:
>
> hi thierry,
>
> > SQUID 2.3S1.
> >
> > We try to bind it on a secondary IP address (http_port xx.xx.xx.xx:yyy)
> > on the internal
> > interface of a proxy (Solaris 2.6).
> > Squid core dumps on startup (segmentation fault).
> >
> > If we specify the port only (http_port yyyy) directive, it works fine.
>
> yes, after i upgraded to squid-2.3.stable1 i run into the same problem.
> solution: add a hostname for your internal ip-address to /etc/hosts. i
> didn't read the source, but i got the impression that squid tries to
> verify it's ip-address on start-up. also: if you want to do redirects for
> virtual hosts on your internal ip-address-based httpd, i recommend
> compiling squid with --disable-internal-dns or you might be running into
> bigger problems..
>
> hope it helps,
> eelco
>
> --
> /* Eelco M. Glasl <emglasl@gmx.net> * ICQ#: 52029132 */
Received on Tue Feb 22 2000 - 23:57:24 MST