last chunck is bigger than maxChunckSize about resumable.js

[sarvigalava]

if file has 1,5MB it is uploaded entirely

[sarvigalava]

fixed with :
var lst=0;
if($.file.size/$.resumableObj.opts.chunkSize>0)
lst=1;

  for (var offset=0; offset<Math.floor($.file.size/$.resumableObj.opts.chunkSize)+lst; offset++) {
    $.chunks.push(new ResumableChunk($.resumableObj, $, offset, chunkEvent));
  }

[sarvigalava]

seems to work but md5sums are different. Need to know if it is a php issue or javascript :(

[sarvigalava]

fixed :
if ($.fileObjSize-$.endByte < 0) {
// The last chunk will be less than chunkSize
$.endByte = $.fileObjSize;
}

[steffentchr]

Actually this is expected behaviour: That the last chunk is bigger than other chunks -- but smaller than 2*chunkSize. This is the case for two reason: To avoid uploads of byte-size chunks and more relevantly to allow for meta detection in the last chunk of a file. This is something we use ourselves to detect whether an upload is a video file, based only on the first and the last chunk of a resumable upload.

[sarvigalava]

my php max file size limitation is 2MB so max chunk size must be 2MB in order to be efficient. I must upload big archive 10-12GB on server with limitation without using ftp. Thanks for script it works awesome. One only question : how to verify server response ?

[steffentchr]

If so, the trick is simply to have set the chunk size to be 1 MB. This will also be efficient enough, even at large files. Not really sure what you mean about verifying server reponse?

[sarvigalava]

I want to send to client error messages (permission denided, already uploaded etc etc)