Pass metadata to backend

@goto-bus-stop Hello, how can I pass meta data information to backend tus node server through uppy tus endpoint ? I want to get that information on my backend server such as file original name, mime type and size so I can rename the file to its original name or whatever filename is set in metaField option in uppy.

On my backend, I get only file id, name (encoded), type (encoded). server.on(EVENTS.EVENT_UPLOAD_COMPLETE, (event) => { console.log(`Upload complete for file ${event.file.id}`); });

[goto-bus-stop]

Renaming the file on backend (node js and express js) after upload is completed by decoding the name as you suggested.

I suggested decoding the upload_metadata property, not the name 😃

Uppy does not have additional requirements beyond what tus-js-client has.

As I understand it the HEAD 404 response is expected when you move the file, and should not affect the upload further.

When I remove the GET method from backend and try to reupload the same file again without deleting the old one, then there are no errors such as HEAD 404 or Refused to get unsafe header “Upload-Offset”

It looks like you were overriding the /upload/files/:fileId route from the tus node server, which may be why you get the error about Upload-Offset. I think that is also why it works correctly when you remove that route, you’re probably not supposed to override it.

I’m a bit lost—it seems like the problem is no longer with reading metadata on the server is it? I’m struggling to piece together what is going wrong / unexpected from the comments so far.

[Acconut]

But I get this behavior only when I remove the GET method from the backend. I hope somebody from uppy team will explain it further.

Ok, since tus-js-client does not do GET requests, this might be caused by Uppy but I cannot help there much 😃