Open slava-uxd opened 8 years ago
Thanks for the report. This is likely caused by Fine Uploader's failure to check the status of the response before attempting to parse the response. In this case, it is likely hitting a request for one chunk in a batch of concurrent file chunks that has been cancelled internally as a result of another chunk failure. The status is most likely 0
, which indicates cancellation and therefore this request will not have a response. The issue appears to be benign. I'll look into including a patch in a future release.
Type of issue: Bug? Uploader type: traditional Fine Uploader version: 5.5.1 Browsers where the bug is reproducible: All Operating systems where the bug is reproducible: Windows 7
Steps to reproduce the issue
xhr.response
andxhr.responseText
are empty insideonError()
callback, which makes other data in the response not readable. AlthougherrorReason
does contain text from a server's 'error' response.Only happens when concurrent chunking is enabled. Non-concurrent chunking = ok. Single-file uploads = ok.