Hello Christian, thanks for reply. :-)

So, I've tested it on Xubuntu 14.04 64 bits and it has worked fine, so it
seems to be a problem related to MHD on Windows. I'm using Windows 7 Pro 64
bits, and MHD was compiled for 32 bits with MingWG-w64 32 bits. To compile
the demo I just opened and compiled it in my CLion, so I think that it
doesn't have an I/O limit, and I have 40 GB on my disk.

I've noticed that the progress stay a long time (~1min) in 99% even on
Linux, but it receive the entire upload.

Can anybody confirm if it's a bug related only to MHD on Windows? :-/

On Tue, Mar 29, 2016 at 3:32 AM, Christian Grothoff <[email protected]>
wrote:

> Hi Silvio,
>
> I just tried a 4699722540 byte file with both Firefox and Chrome on
> GNU/Linux using 'largepost.c', and it worked without a problem.
>
> If you've compiled your own custom application, make sure you've enabled
> large file support for your disk IO.  That said, I've not (recently?)
> tested this on a 32-bit system. Still, MHD should handle large files
> like this.
>
> As far as file limits are concerned, the MHD_PostDataIterator is limited
> to 2^64-1 bytes. MHD itself has no limit as it has no concept of files
> and treats requests as a possibly infinite stream of data. However, this
> requires that the client does NOT set "Content-Length" (but use chunked
> encoding). If "Content-Length" is present, the limit is again 2^64-1.
> Note that technically HTTP doesn't impose the 64-bit limit on HTTP, but
> I'm not aware of any HTTP client or server supporting > 64-bit values here.
>
>
> Happy hacking!
>
> Christian


-- 
Silvio Clécio

Reply via email to