Bugs item #2254709, was opened at 2008-11-10 11:11
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2254709&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: https
Group: wrong content
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Vincent FIACK (vfiack)
Assigned to: Daniel Stenberg (bagder)
Summary: uploading a very small file fails

Initial Comment:
Uploading a small file fails with https, resulting in an empty file instead of a small one.

Steps to reproduce:
echo "test" > small.txt
curl -k -F file=@small.txt https://www/upload.jsp

We get the correct filename, with empty content.

The same with http works perfeclty. The same with a standard browser (IE or firefox) works as expected.

Using a file with 60 bytes of contents works as expected.

Versions used:
* curl 7.12.1 (i386-redhat-linux-gnu) libcurl/7.12.1 OpenSSL/0.9.7a zlib/1.2.1.2 libidn/0.5.6

* curl 7.19.0 (i386-pc-win32) libcurl/7.19.0 OpenSSL/0.9.8h zlib/1.2.3
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: Largefile NTLM SSL SSPI libz

Notes:
the server certificate is invalid (self-signed)

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2008-11-10 13:07

Message:
I think the problem is in your receiving end. Use the --trace or
--trace-ascii option to get a complete protocol "dump" and it should tell.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2254709&group_id=976
Received on 2008-11-10