-
Notifications
You must be signed in to change notification settings - Fork 144
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
Problem with :filename #146
Comments
👍 Just ran into this issue in production |
Fixed in #150 |
Well, I finally got hit by this bug a year later. It also affects any filename with a % in it, which it turns out certain disreputable browsers use to save images, e.g. "my%20face.jpg". It seems like a rather critical issue. @benallfree Do you still intend to refactor #150 or would you like me to do it? I actually already did it for my own project, but I had to make my own |
I believe #167 fixes this whole issue because filesystem names are no longer based on the URL name. |
Hello
I come across to problem when I'm using special (diacritics and white space) characters in filename.
but if its in
<img src={{$path}}
> server throws 404 Not Found Exceptionbecause its trying to fetch
Sn%C3%ADmek%20obrazovky%202015-10-16%20v%2013.00.24.png
I thing it will be great feature if configuration has option :safeFilename which converts original filename to ASCII
The text was updated successfully, but these errors were encountered: