[squid-users] cannot use squid-3.5.x for production

[Tom Tom]

Hi Othmar

The same behaviour here with squid 3.5.5:

# Catching an existing file results in a correct 200:
$ curl -x proxy:3128 -I ftp://mirror.switch.ch/README
HTTP/1.1 200 OK
Server: squid
Mime-Version: 1.0
Date: Wed, 01 Jul 2015 07:58:28 GMT
Content-Type: text/plain
Last-Modified: Wed, 05 Dec 2007 14:13:16 GMT
X-Cache: MISS from proxy
Connection: keep-alive


# Catching an non-existing file hangs for a unknown time
$ curl -x proxy:3128 -I ftp://mirror.switch.ch/README123


I can confirm, that with older squids (< 3.5) catching a
non-existing-file with ftp gives back a correct 404.

Kind regards,
Tom

On Wed, Jul 1, 2015 at 8:43 AM, truniger at bluewin.ch <truniger at bluewin.ch> wrote:
> Not much reaction on my statements so far.
> So let me ask: is anyone actually receiving a valid 404-http-response from squid 3.5.x when trying to download a file which does not exist on the FTP-server?
> I don't and I think it's a bug with 3.5.x and I wonder why I seem to be the only one facing it.
>
> Regards, Othmar
>
>>The problem: when trying to FTP-download a non-existing file the
>>client-http-connection just hangs forever. The external FTP
>>communication works fine but squid misses to send back a http-response with code 404.
>>Instead the connection just stays open.
>>I have several jobs in production polling for files on external FTP
>>servers which work fine with 3.4.x but cannot be used anymore on 3.5.x
>>
>>Would be nice if someone could confirm this problem and even better if
>>someone has a valid 3.5.x workaround for this.
>
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users