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
Cannot open files with spaces in name #1501
Comments
This is a setup specific issue caused by wrong encoding. |
Sorry, could you please elaborate what I did wrong? |
The problem does not occur with nginx and is due to some kind of wrong encoded URI send from your webserver to Seafile. |
Hi @shoeper, thanks, ok, answer accepted, still I don't consider it fair to close a bug report, just because it works on your setup. We use apache in front of seafile and use no options, which would contradict with what is written in the server manual. Here is the vhost config:
Don't get me wrong, I report this issue here not because I want to steal your precious time, but because I want to make this product better. Even if the solution is to put a note/hint/warning in the docs that some certain setup will cause troubles. Do you need any more information in order to tackle the culprit? |
Can you try this (Source: #1258) |
Yes works! Thank you very much. This should really be noted in http://manual.seafile.com/deploy_windows/deploy_with_apache.html. (I swear I searched for existing tickets first, but obviously didn't realize the referenced ticket.) |
Maybe you can work on a pr for the seafile server manual repo. |
Will do! |
@shoeper Check https://github.com/haiwen/seafile-docs/pull/151 please. |
For anyone using Apache pre 2.4.11 (like Debian stable/jessie) the solution via apache config
Don't forget to enable unquote_path_info in your wsgidav configuration if using webdav... |
Hi @hede5562 this works for us as well (Debian Jessie). Thanks for the info. Will this fix make it in the next Seafile release, or do we have to do this again after next update? Thanks again! Great job! |
Hey @antares2001, as i see you must also redo this for the next version. I was at the same point at the moment after upgrading to 6.0.7, had the exact same situation as described here.
|
Hi @hede5562, thanks for the very helpful information.
Which file(s) and what should there be changed/edited? |
Hi everyone, I just had the same issue on my server, and since I am running Ubuntu 14.04 and thus was on apache 2.4.7, I used Ondrej's repo to upgrade to the newest stable apache2 (as suggested here)
Fixed the issue :) |
I spent a lot of time to solve this problem and there is an easy solution; If this problem happens when you have Ubuntu 14.0x install, do a upgrade to the latest version with the command; do-release-upgrade |
@evdbovenkamp I'd argue that doing a release upgrade is not "easy" at all ^^ depending on your setup, it can break EVERYTHING. But it's an alternative solution, that's true ;) |
When I try to click on a file in the web-ui which has a space in its name I get a 503 error.
Example URL:
https://example.com/lib/a7dad841-1f33-4ca0-a50c-80f203455c99/file/TYPO3%20Update%20cmdline.txt
seahub_django_request.log holds:
The text was updated successfully, but these errors were encountered: