Open meness opened 4 years ago
I don't have time to test this right now, so if you have any ideas what could be causing the issue that would be very helpful
@meness Did you find a workaround or a solution to your problem? I'm currently facing the same problem, with the only difference being, that I'm using the VUE-Adapter instead of React.
So I debugged it today to see what exactly is happening and filepond is in fact working correctly.
In my case it was an error caused by ExpressJS in the backend, because I didn't set:
res.set('Access-Control-Expose-Headers', 'Upload-Offset');
Filepond received null
, when trying to read the response header by xhr.getResponseHeader("Upload-Offset")
and defaulted to using 0
as Offset.
Docs say if chunks failed, the client requests
HEAD
and the server must returnUpload-Offset: <offset>
, then the client mark lower chunks as completed, but in my case, the client starts from 0 once again while I send the header with a right offset.React
Express
My test is: I write
500000
bytes then throw an error. When the client requests aHEAD
I tell it the offset is500000
, but it starts from0
.I use the latest version.