mån 2011-01-10 klockan 16:19 -0700 skrev Alex Rousskov:
I seem to recall reports that the proxy was still working fine despite
the lookup errors so we should be careful not to disable useful
functionality. There is probably more than one way to lookup the
destination, and as long as one way
On 12/01/11 13:53, Alex Rousskov wrote:
On 01/07/2011 06:04 PM, Amos Jeffries wrote:
Note that a great many hostnames are localhost or
localhost.localdomain or localhost.local due to certain distros
hard-coding localhost into their packages.
We also use localhost as a backup when the
On 01/11/2011 07:13 PM, Amos Jeffries wrote:
On 12/01/11 13:53, Alex Rousskov wrote:
On 01/07/2011 06:04 PM, Amos Jeffries wrote:
Note that a great many hostnames are localhost or
localhost.localdomain or localhost.local due to certain distros
hard-coding localhost into their packages.
We
On 06/26/2009 11:00 PM, Amos Jeffries wrote:
Alex Rousskov wrote:
Hello,
Squid detects forwarding loops in most configurations, but breaks
them (using a customizable HTTP_FORBIDDEN response) only when working as
an accelerator. Squid does not break loops when working as a transparent
Hello,
Squid detects forwarding loops in most configurations, but breaks
them (using a customizable HTTP_FORBIDDEN response) only when working as
an accelerator. Squid does not break loops when working as a transparent
proxy. Interestingly enough, the breaking code comment (in the patch
Alex Rousskov wrote:
Hello,
Squid detects forwarding loops in most configurations, but breaks
them (using a customizable HTTP_FORBIDDEN response) only when working as
an accelerator. Squid does not break loops when working as a transparent
proxy. Interestingly enough, the breaking code
