> It is probably a good time to run a "squid -k debug" dump to verify that
> your Squid is properly identifying the connection as intercepted and
> resolving the original destination IP.
Ok. One thing I noticed is these three mime_get_header rows that is seen in squid-2.5
but not in squid-3.0
On Tue, 28 Sep 2004, Andreas Pettersson wrote:
Is there anything at all in cache.log which may be relevant?
Earlier the following occured, but I'm not sure exactly what configuration I was
running at the time (I have tested a LOT of different configurations.. I might have
run some stupid conf..)
> Is there anything at all in cache.log which may be relevant?
Earlier the following occured, but I'm not sure exactly what configuration I was
running at the time (I have tested a LOT of different configurations.. I might have
run some stupid conf..)
2004/09/28 11:36:37| Failed to select sourc
On Tue, 28 Sep 2004, Andreas Pettersson wrote:
http_port 127.0.0.1:80 transparent
This is not working. "Invalid URL" (NONE/400 1749 GET / - NONE/- text/html)
Is there anything at all in cache.log which may be relevant?
Since the redirection has proven to be working I assume there's something wrong
> > it stops working. The browser indicates that it has contact with the web server,
> > but nothing happens. After some time this may appear in access.log:
> > TCP_MISS/000 0 GET http://idg.se:8090/ - NONE/- -
>
> If it gets this far the redirection works but something prevents Squid
> from mak
On Tue, 28 Sep 2004, Andreas Pettersson wrote:
it stops working. The browser indicates that it has contact with the web server, but
nothing happens. After some time this may appear in access.log:
TCP_MISS/000 0 GET http://idg.se:8090/ - NONE/- -
If it gets this far the redirection works but someth
> When running Squid-3 instead the problem is these log entries:
> NONE/400 1749 GET / - NONE/- text/html
> which of course generates "Invalid URL" in the browser.
I forgot to mention, there's no errors in cache.log.
/Andreas
> The error indicates Squid does not realize these connections have been
> transparently intercepted.
>
> Make sure you have the correct --enable-- option for integrating Squid
> with your OS firewall, and no related errors in cache.log.
>
> Regards
> Henrik
Good point. I had missed that. Howe
On Sun, 26 Sep 2004, Andreas Pettersson wrote:
squid.conf:
http_port :8093 transparent vhost
Don't use the vhost directive. This is for accelerator mode, not
transparent proxies.
Regards
Henrik
Hi all.
I thought it was about time to do some heavy testing of Squid-3 (3.0-PRE3-20040830),
but almost immediately I ran into problems..
I'm using FreeBSD 5.1 as a gateway with 2 NICs and has set up the following ipfw rules:
allow tcp from to any
allow tcp from to any
fwd ,8093 tcp from to a
10 matches
Mail list logo
