Re: [squid-users] Squid cURL FTP SSL Problem

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Sun, 14 Sep 2008 03:43:46 +1200

James W. Guillot wrote:
> Squid has worked reliably for us for years and we love it! But I am having
> a problem sending files larger than 32k using ftp/ssl. I’m using:
> Squid-2.5.STABLE9
> cURL 7.19
> Host is a Sterling commerce server.
>
>
> Curl Command is as follows:
> Curl –T text.txt --trace-time --trace-ascii results.txt -p --use-ascii
> --disable-epsv --cacert ca-bundle.crt --cert XXX.crt:crtpasswd --key
> XXX.pem --ftp-ssl -x proxyserver:port
> ftp://userid:passwd@Somewhere.com:10021
>
> Here’s the error we are getting:
> 0e8f: Curl 7.19.0 10 July 2008 25
> 21:54:09.387000 == Info: Remembering we are in dir ""
> 21:54:09.387000 == Info: SSLv3, TLS alert, Client hello (1):
> 21:54:09.387000 => Send SSL data, 2 bytes (0x2)
> 0000: ..
> 21:54:09.824000 <= Recv header, 54 bytes (0x36)
> 0000: 226 [-6996] SSLRead: SSLProtocolErr: Protocol error.
>
>
> I can successfully send smaller files using squid, but files
> larger than 32k fail. I can use the same cURL command and bypass the Squid
> proxy server to successfully send files larger than 32k. So the problem
> seems to be with the Squid proxy server. Any ideas on what to look at?
>

Check squid.conf for maximum object size parameters.
Then read up on any you find of about 32K.
Its probably maximum_request_body_size

You might also try a more recent Squid. Things have made a lot of
improvement since 2.5.

Amos

-- 
Please use Squid 2.7.STABLE4 or 3.0.STABLE9
Received on Sat Sep 13 2008 - 15:43:55 MDT

This archive was generated by hypermail 2.2.0 : Sat Sep 13 2008 - 12:00:03 MDT