Maybe I'm saying something stupid but 2G is awfully close to maxint. Maybe
there is a count of bytes read/available somewhere that use an int and should
use a long instead.
Just an idea that crossed my mind.
_
Comme 9 millions
Eric Cantonna wrote:
Maybe I'm saying something stupid but 2G is awfully close to maxint. Maybe
there is a count of bytes read/available somewhere that use an int and
should use a long instead.
Just an idea that crossed my mind.
Right. But since it's HTTPClient's executeMethod()
On Tue, 2008-03-11 at 11:38 -0700, sjlucas wrote:
Eric Cantonna wrote:
Maybe I'm saying something stupid but 2G is awfully close to maxint. Maybe
there is a count of bytes read/available somewhere that use an int and
should use a long instead.
Just an idea that crossed my mind.
quote
Some servers (IIS) require the client to use chunked file transfer
encoding to transfer files larger than 2G. If you are not using
chunked try that
Could you point me to an example of how to specify to use chunked file
transfer with HttpClient on a GET request?
--
View this message
sjlucas wrote:
Could you point me to an example of how to specify to use chunked file
transfer with HttpClient on a GET request?
It should be the default if you are connecting to the server
using HTTP/1.1. Chunked encoding does not exist in HTTP/1.0.
hope that helps,
Roland
Is this a known limitation in HttpClient? Or, do I need to do something
different when getting a file 2G ?
Some servers (IIS) require the client to use chunked file transfer
encoding to transfer files larger than 2G. If you are not using
chunked try that
