Re: [squid-users] cannot use squid-3.5.x for production
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@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] cannot use squid-3.5.x for production
Thanks Tom, as I described in Bug-Id 4279, the whole external FTP communication is working and completed perfectly, as with older releases. It's just that the FTP result status is not put into any http-response. Instead the client-proxy connection stays open 'forever'. Othmar ># 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 ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
