-
Notifications
You must be signed in to change notification settings - Fork 8
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
Issue with +
in filename
#45
Comments
Probably need to use quote_plus |
Issue is also when opening h5web with a double click from the file browser. |
After thorough investigation, the escaping happens when the request URL is parsed on the backend. The culprit is tornado's parse_qs_bytes that parses arguments expecting them to be URL-encoded. >>> parse_qs_bytes('file=stack+.h5&path=/')
{'file': [b'stack .h5'], 'path': [b'/']}
>>> parse_qs_bytes('file=stack%2B.h5&path=%2F')
{'file': [b'stack+.h5'], 'path': [b'/']} To avoid problems of this type in the future, we should ensure that the filename is encoded every time it roundtrips between the front-end and the back-end. This means encoding should happen in the following situations:
|
Fixed by silx-kit/h5web#774 and silx-kit/h5web#781 |
Running
H5Web("new_file+d.h5")
from a notebook leads to opening "new_file d.h5" on the server side (its already changed in the GET request).Logs on the server side:
The text was updated successfully, but these errors were encountered: