You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue with socketio-file-upload, but is an issue others may run into when uploading files.
I found that my Microsoft Edge users would end up with files on my server with junk timestamps. In my case, I have a process that rsyncs the files to another location and preserves timestamps. rsync would fail with a message like the one below--substitute your file name.
In short, the object is missing the "lastModified" property that normally holds the unix time value. In my own code, I was able to account for this by adding this bit of code in my function where I handle each file object:
if (!file.lastModified) { file.lastModified = file.lastModifiedDate.getTime(); }
Arguably, socketio-file-upload client could do this same thing internally.
The text was updated successfully, but these errors were encountered:
This is not an issue with socketio-file-upload, but is an issue others may run into when uploading files.
I found that my Microsoft Edge users would end up with files on my server with junk timestamps. In my case, I have a process that rsyncs the files to another location and preserves timestamps. rsync would fail with a message like the one below--substitute your file name.
Time value of %s truncated on receiver.
The issue is that Edge does not follow the spec for the File Object as explained here:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/4155006/
In short, the object is missing the "lastModified" property that normally holds the unix time value. In my own code, I was able to account for this by adding this bit of code in my function where I handle each file object:
if (!file.lastModified) { file.lastModified = file.lastModifiedDate.getTime(); }
Arguably, socketio-file-upload client could do this same thing internally.
The text was updated successfully, but these errors were encountered: