tomdesair
commented
5 years ago Hi @softboy99,
The tus protocol itself makes abstraction of files: "the specification does not have the principle of a disk-based file, allowing you to upload arbitrary data using tus" (https://tus.io/protocols/resumable-upload.html#how-can-i-get-the-file-name-or-file-type-for-an-upload). This means the tus Java server implementation cannot rely on the fact that an upload is always a "file". It could also be for example a video stream.
In addition, you should always consider the upload directory as a temporary directory. You should not use it as the permanent destination of the uploaded bytes.
However, the Uppy file uploader does provide the filename as metadata. The tus Java server implementation supports this through the getFileName() method. But note that this method only gives a meaningful value if you upload files with Uppy (or any other uploader that passes the filename as metadata). So if you are uploading files with Uppy, you could copy the uploaded bytes to their final destination in a new file with the correct name.
For example we could extend the Dropwizard example to
if(!uploadInfo.isUploadInProgress()) {
InputStream uploadedBytes = tusFileUploadService.getUploadedBytes(url, ownerKey);
Path newFile = Paths.get("my/target/directory", uploadInfo.getFileName());
java.nio.file.Files.copy(
uploadedBytes,
newFile,
StandardCopyOption.REPLACE_EXISTING);
//Since we're done with processing the upload, we can safely remove it now
tusFileUploadService.deleteUpload(url, ownerKey);
}Does this answer your questions?
softboy99
How to make the uploaded file on the server with corrected file extension? Currently, the uploaded file on the server has no file extensions. All of them is named "data".