Waitman Gobble wrote:
Hi,
I've heard word from a cohort in Mexico who is *sometimes* receiving
instant/abrupt 'no conecto' messages, curious if it's possibly an issue
between the two squids. It does not appear to be random, it seems to
happen with specific requests.
However, it doesn't make sense to me that there would be such an issue.
mx - 1.1 cache22.gdl.megared.net.mx:80 (squid/2.6.STABLE13) {'prolly a
perimeter cache in mx}
The above squid appears to have at minimum an experimental patch for
showing ports in Via: applied. Only the admin knows what else its doing.
It may also doing transparent interception on port 80 using port 80 as
the input port. This can screw things in weird ways if the someone
connects directly to the machine itself on port 80.
ca/us - 1.0 a.ujena.net (squid/3.0.STABLE15)
HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES;
rv:1.9.0.12) Gecko/2009070611 Firefox/3.0.12
HTTP_ACCEPT
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
HTTP_ACCEPT_LANGUAGE es-es,es;q=0.8,en-us;q=0.5,en;q=0.3
HTTP_ACCEPT_ENCODING gzip,deflate
HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7
HTTP_VIA 1.1 cache22.gdl.megared.net.mx:80 (squid/2.6.STABLE13), 1.0
a.ujena.net (squid/3.0.STABLE15)
HTTP_CACHE_CONTROL max-age=259200
HTTP_CONNECTION keep-alive
That is an (incomplete) interpreted version of the headers. Nothing
unusual showing. If its a problem with the headers its not visible there.
It may be either of the Squid hitting a problem and restarting though.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE17
Current Beta Squid 3.1.0.12
