Re: [squid-users] local_ip and local_domain unrecognized in 2.4.1 Stable 1

Thanks,

That fixed the syntax but not the problem.
Perhaps I should explain a little more about
the nature of the problem.
What we have is an issue where some of our
end users are unable to login to secure
sites that require a user name and password
or any login page that uses a POST method
(e.g. a web page that allows you to send
messages to a pager or cell phone)
The users report that they can see the page,
it displays correctly but when they press
the "submit" button, nothing happens.
However if they unroute the traffic from the
squid cache, they can visit these same pages
and the "submit" functions work perfectly.
So, we were attempting to force those sites
to go direct but it does not seem to have
any affect. The users still report the problem
even with the domain set to go direct.
(Keeping in mind that it works fine without squid in the mix)

Any suggestions as to what may cause this?

Thanks!

Duane Wessels <wessels@squid-cache.org> said:

>
>
>
> On Mon, 16 Jul 2001 jbarnes@onsatnet.com wrote:
>
> > Hello,
> >
> > We are running 2.4.1-Stable 1 and have found that
> > local_ip and local_domain do not seem to work.
> > Have these options been deprecated in favor of
> > something else or is the documentation not complete
> > in its description of this feature? The way I understand
> > it, you should only need to enter the following in .conf
> >
> > local_domain somedomain.com
> > local_ip 123.12.1.1
> >
> > However after entering this and running
> > squid -k parse
> > it complains that these lines are unrecognized.
> >
> > Any suggestions or help would be much appreciated.
>
> See http://www.squid-cache.org/Doc/FAQ/FAQ-19.html#ss19.11
>

--