-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
Spaces in filenames causes 400 bad request #170
Comments
Ok so I managed to get it to work by changing the filename before being uploaded via:
In my Uppy config however this is not ideal as I would like to preserve the original filename. I guess I could add the original name to the meta data and convert it back at the server end once fully uploaded but still wondering if there's a way to avoid all this extra hassle? |
@ankitpokhrel There you go :) Yeah, spaces should not trigger validation error :) They should not allow one to break out of a directory. |
Nice one, thank you! :) |
Same error with quote in filename. Ex. |
Quotes are explicitly forbidden in the code. I've taken a look what characters are actually forbidden in filesystems and quotes will fail on Windows. Apparently they are acceptable on Linux 🤔 https://stackoverflow.com/a/31976060/2424641 @ankitpokhrel should we relax the checks a bit? |
@Steveb-p There is an open issue to make this configurable. I am open to PR :) |
When using Laravel, php-tus and Uppy, everything is working fine until I drag-drop a file that has space characters in the filename.
I have autoProceed set to true and the file attempts to be uploaded but tus-php returns a 400 bad request. If I remove the space(s) from the filename and retry it works without issue.
I followed the Laravel/Lumen integration guide so my routes files looks like:
My TusServiceProvider.php is as follow:
And my Javascript is as follow:
The text was updated successfully, but these errors were encountered: