On Mon, 25 Nov 2002 RBramante_at_on.com wrote:

> It looks like infilesize is defined as long, so effectively setting
> CURLOPT_INFILESIZE limits you to 2 GB on most systems.

Or at least 4GB if we switch over to unsigned all over.

> Does HTTP limit content length to 2 GB or is this just a curl decision?

That is a curl limitation. Feel free to fix.

> We may potentially be putting very large files to an HTTP server. Will I
> need to insure to send these as chunked encoded so as to not overflow
> infilesize?

That would be one way to overcome this limitation in curl, sure.

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf