-
Notifications
You must be signed in to change notification settings - Fork 51
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
downloadFolder not working with special charater #71
Comments
Yes, the handling of special characters is not consistent at the moment. |
For the encoding part as buildWebdavPath is using a URIbuilder I think it is better to always use this function before sending something in sardine. |
Here are the changes only for downloadFolder using buildWebdavPath before sardine call (both directory and file can have a space now):
|
Any chance you can send mit a diff file? |
Here is the diff Folder.java.txt. there is some noise due to my IDE reformating Unit test were not working (I added the setting.xml but still, wrong plugin version ?) so I disabled them and It will be hard to check if they work. |
Looks like it fixes the problem, thanks Can you test with the 11.7.0-SNAPSHOT release? |
Yes version 11.7.0-SNAPSHOT solves this issue, thanks. It also solve the issue we had from 11.6.0 it seems. |
Yes, it should also solve the problem with login name not identical to the NC internal user name in issue #68 The drawback is, that we have to ask the server what the user name of that user is, before we can work with files in NC, but there is no way to know this for sure, so that's the only real working solution. |
12.0.0 works fine, thanks |
We are using the org.aarboard.nextcloud.api.NextcloudConnector.downloadFolder function and had an issue with the special character. For example for the filename "MobaXterm backup.zip" sardine.exists gave us a malformated URI exception because space was not escaped.
We tried to use the buildWebdavPath but it seems complex to use as the function is called previously on the root path.
I will try to make the pull request work this time if not will edit the issue with the code we used to correct it.
Thanks
The text was updated successfully, but these errors were encountered: