Daniel,

Thanks for your first reply. I've now altered the upload command to the
following, incorporating the trace-ascii flag;

/usr/local/bin/curl -# -S -v -F "username=<username>" -F
"password=<passwd>" \
-F "file=@/<filename>.tar.gz;type=application/x-gzip" \
--proxy-anyauth -x "<proxy>:8080" --trace-ascii "/<trace-ascii-output>"
\
https://www.webaddress > /<upload-output-file>

 However, when I look at the output file I still get a pretty simplified
error message;
<output cut>
== Info: About to connect() to proxy <proxy server> port 8080 (#0)
== Info: Trying <proxy IP address> ... == Info: connected
== Info: Connected to <proxy server> (proxy IP address) port 8080 (#0)
== Info: Establish HTTP proxy tunnel to www.webaddress:443
=> Send header, 189 bytes (0xbd)
0000: CONNECT www.webaddress:443 HTTP/1.0
0027: Host: www.webaddress:443
0043: User-Agent: curl/7.16.1 (sparc-sun-solaris2.10) libcurl/7.16.1 O
0083: penSSL/0.9.8d zlib/1.2.3
009d: Proxy-Connection: Keep-Alive
00bb:
<= Recv header, 37 bytes (0x25)
0000: HTTP/1.1 200 Connection established
<= Recv header, 22 bytes (0x16)
0000: Via: 1.1 <proxy hostname>
<= Recv header, 24 bytes (0x18)
0000: Connection: Keep-Alive
<= Recv header, 30 bytes (0x1e)
0000: Proxy-Connection: Keep-Alive
<= Recv header, 2 bytes (0x2)
0000:
== Info: Proxy replied OK to CONNECT request
== Info: successfully set certificate verify locations:
== Info: CAfile: /usr/local/share/curl/curl-ca-bundle.crt
  CApath: none
== Info: SSLv2, Client hello (1):
=> Send SSL data, 106 bytes (0x6a)
0000: ....Q......9..8..5..............3..2../.........................
0040: ....@.......................-..Xl...1..NOd
== Info: SSLv3, TLS handshake, Server hello (2):
<= Recv SSL data, 74 bytes (0x4a)
0000: ...F..G........P..|..U........XM...Sn. L)..8Y.Gg...E..(./..l....
0040: ..>imh..9.
== Info: SSLv3, TLS handshake, CERT (11):
<= Recv SSL data, 3499 bytes (0xdab)
0c52: )....l...S.Y.sM..)..-.&u..w?zV...$.O9+..k.....Xk3....,.Nn....>l@

<...output cut...>

09c0: ......`lo....2..Z..W.7....oo.......q..6~...r..8.{.....}.[..?I.
0a00:..q..6~n|4....o.=.....Npv.&.#
=> Send data, 48 bytes (0x30)
0000:
0002: ------------------------------97492e51631d--
<= Recv header, 17 bytes (0x11)
0000: HTTP/1.1 200 OK
<= Recv header, 37 bytes (0x25)
0000: Date: Wed, 27 Feb 2008 16:25:13 GMT
<= Recv header, 70 bytes (0x46)
0000: Server: Apache/1.3.28 (Unix) PHP/4.3.4 mod_ssl/2.8.15 OpenSSL/0.
0040: 9.7b
<= Recv header, 25 bytes (0x19)
0000: X-Powered-By: PHP/4.3.4
<= Recv header, 28 bytes (0x1c)
0000: Transfer-Encoding: chunked
<= Recv header, 40 bytes (0x28)
0000: Content-Type: text/html; charset=utf-8
<= Recv data, 18 bytes (0x12)
0000: 6
0005: ERROR.
000d: 0
0010:
== Info: Connection #0 to host isaproxy.ad.cazenove.net left intact
== Info: Closing connection #0
== Info: SSLv3, TLS alert, Client hello (1):
=> Send SSL data, 2 bytes (0x2)
0000: ..
<!output cut>

Now from the above output, I can't see what the actual error is apart
from the work "ERROR". Is there another way of narrowing down where the
fault is that I'm getting? One thing I have noticed is that when I send
a 10Mb file, the curl command with all the options that I've got above
works, but when I'm trying to send a file of length 40Mb it fails.

David
-----Original Message-----
From: curl-users-bounces_at_cool.haxx.se
[mailto:curl-users-bounces_at_cool.haxx.se] On Behalf Of Daniel Stenberg
Sent: 26 February 2008 22:59
To: the curl tool
Subject: Re: Https upload error

On Tue, 26 Feb 2008, Cassin, David M wrote:

> Trying to upload a file using curl, and all that I'm getting as an
> error message is;

> ERROR
> - DEBUG: upload error nr. 3 (The uploaded file was only partially
> uploaded)

Use --trace or --trace-ascii and verify if that statement is true or
not.

> /usr/local/bin/curl -v -K <upload_reference_file> \ -proxytunnel -F
> "DEBUG=Ben" -F "file=@${a};type=application/x-gzip"

-K is for specifying a "config file" to read more options from. It seems
odd to call that "upload_reference_file".

> This e-mail is confidential and is for the addressee only.

Confidential materials aren't that suitable to post to public mailing
lists...

--
  Commercial curl and libcurl Technical Support:
http://haxx.se/curl.html
This e-mail is confidential and is for the addressee only.  Please refer to www.jpmorgancazenove.com/disclaimers/jpmorgancazenove.htm for important disclaimers and the firm's regulatory position.