Difference between revisions of "ownCloud/client"
< ownCloud
Jump to navigation
Jump to search
(moved problem discussion link here, since it was a client issue) |
(diagnosis with wget) |
||
| Line 3: | Line 3: | ||
It also seems to store copies of most or all synced files in the same folder, <code>$HOME/.local/share/data/ownCloud/</code>, which seems rather wasteful of disk space as well as completely unnecessary. (To be investigated in more detail later...) | It also seems to store copies of most or all synced files in the same folder, <code>$HOME/.local/share/data/ownCloud/</code>, which seems rather wasteful of disk space as well as completely unnecessary. (To be investigated in more detail later...) | ||
| + | ==Diagnosis== | ||
| + | * You can use [[wget]] to simulate [[WebDAV]] requests: | ||
| + | ** <code>wget https://{{arg|hostname}}/owncloud/remote.php/webdav/ --no-check-certificate --user={{arg|username}} --password={{arg|password}} --method=PROPFIND</code> | ||
| + | |||
==Outlinks== | ==Outlinks== | ||
* Discussion: | * Discussion: | ||
Revision as of 18:51, 6 August 2015
Linux
In Linux, the client stores its configuration in $HOME/.local/share/data/ownCloud/owncloud.cfg[1].
It also seems to store copies of most or all synced files in the same folder, $HOME/.local/share/data/ownCloud/, which seems rather wasteful of disk space as well as completely unnecessary. (To be investigated in more detail later...)
Diagnosis
- You can use wget to simulate WebDAV requests:
wget https://<hostname>/owncloud/remote.php/webdav/ --no-check-certificate --user=<username> --password=<password> --method=PROPFIND
Outlinks
- Discussion:
- 2015-08-06 Woozle: trying to figure out why client incorrectly reports bad credentials (Solved: turned out to be a bug in the client, fixed in latest download.)