-
-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Two files same filename #406
Comments
Hi @MichalKrakow, you need to organize your uploads in the server to prevent that from happening. See #79 and #52. |
Thanks for taking Your time to response ❤️ So to wrap it up for future users lets say: Thanks, its clear to me now - but still documentation should point it out, especially considering that default configuration without this piece of code will introduce bugs to this library users code logic. Best regards, |
This issue has been automatically marked as stale because it has not had |
Closing because of inactivity. |
Describe the bug
It's probably documentation issue cause i find it hard to belive this is not yet addressed.
When uploading same file, or event different file with the same filename, server does not provide any obvious way to address the issue and increment filename with some suffix. TUS specification say, the file location is being estabilished with first response to client so at this point we should have some way to check if file does not exist in storage already and change the incoming file destination filename. It should be event automatically resolved by server with some way to override by configuration.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
File with suffix should be stored in storage
So if this feature is already in place, please make it stand out in documentation since lack of it makes this library useless.
The text was updated successfully, but these errors were encountered: