Re: [squid-users] (un)expectefd behaviour

On Sat, 20 Jun 2009 20:09:23 +0200, Matus UHLAR - fantomas
<uhlar_at_fantomas.sk> wrote:
> Hello,
>
> I wonder that trying to fetch some kind of content via squid results into
> closing connection w/o any comment:
>
> % telnet proxy1.nextra.sk 3128
> Trying 195.168.1.136...
> Connected to proxy1.nextra.sk.
> Escape character is '^]'.
> GET
ftp://64.50.238.52/.1/ubuntu/pool/universe/d/dcc/dcc_1.3.42.orig.tar.gz
> HTTP/1.0
>
> Connection closed by foreign host.
>
> lynx reported:
>
> Looking up proxy.nextra.sk:3128
> Making HTTP connection to proxy.nextra.sk:3128
> Sending HTTP request.
> HTTP request sent; waiting for response.
> Alert!: Unexpected network read error; connection aborted.
> Can't Access
> `ftp://64.50.238.52/.1/ubuntu/pool/universe/d/dcc/dcc_1.3.42.orig.tar.gz'
> Alert!: Unable to access document.
>
> access log:
>
> 1245520796.296 3100 195.168.3.66 TCP_MISS/000 0 GET
> ftp://64.50.238.52/.1/ubuntu/pool/universe/d/dcc/dcc_1.3.42.orig.tar.gz -
> DIRECT/64.50.238.52 -
>
>
> no error in cache log...
>
> tried with 3.0.14 to 3.0.16, gentoo on x86_64... I know that the file
does
> not exist but should saquid really close the connection?
>
> Ani hints how to debug the issue?

I'm aware of the cause for this but stil lookign for a clean complete
solution. Triggers all appear to be side effects of incorrect mapping FTP
errors to HTTP errors. The lack of FTP auth popups turns out to be one.
I'm slowly working through them as encountered.
http://www.squid-cache.org/bugs/show_bug.cgi?id=2395

To locate the FTP error which is not showing up (you said non-existing
file, thats probably it). Trace with level debug_options ALL,1 9,9.

Amos
Received on Sun Jun 21 2009 - 01:10:30 MDT