[WIP] Cargo Dock, a two-paned Sailfish filemanager with Dropbox and WebDAV - Page 8 - maemo.org

pycage | # 71 | 2014-04-29, 19:01 | Report

This is the first Cargo Dock test version with WebDAV support. Tested successfully with Telekom Cloud (SSL + Basic Auth). Yay!

Please let me know if and where you have problems with WebDAV. And also where it works!

https://dl.dropboxusercontent.com/u/...-1.armv7hl.rpm

The Following 7 Users Say Thank You to pycage For This Useful Post:
clovis86, Leinad, Manatus, minimos, reinob, richardski, rob_kouw

rob_kouw | # 72 | 2014-04-29, 19:52 | Report

Hi pycage, I like your Cargo Dock a lot. Just discovered Dropbox support, great.
A question: could we have a shortcut to /home/nemo, for instance in the Developer Mode section? It is not easy now to get into the other folders over there. Thanks!

The Following User Says Thank You to rob_kouw For This Useful Post:
richardski

pycage | # 73 | 2014-04-29, 20:17 | Report

Originally Posted by rob_kouw View Post

Hi pycage, I like your Cargo Dock a lot. Just discovered Dropbox support, great.
A question: could we have a shortcut to /home/nemo, for instance in the Developer Mode section? It is not easy now to get into the other folders over there. Thanks!

Just make a shortcut. Go to /home, and press and hold on nemo, while the other side has the Places page open. Select Bookmark.

The Following User Says Thank You to pycage For This Useful Post:
rob_kouw

Leinad | # 74 | 2014-04-29, 20:38 | Report

Dropbox support is great! Thanks

Some suggestions for further development (if possible):

show folders before files
show hidden files / folders in all views, when DM is enabled
move files
share / send files (bluetooth, email, ...)
zip / unzip files
open terminal in current folder

Thanks!

Last edited by Leinad; 2014-04-29 at 20:44.

Manatus | # 75 | 2014-04-29, 21:28 | Report

No luck with Owncloud version of webdav. CargoDock is able to establish network connection, but something goes wrong during the login phase. I'll log stuff tomorrow...

The Following User Says Thank You to Manatus For This Useful Post:
pycage

clovis86 | # 76 | 2014-04-29, 22:20 | Report

which OC release version did you try with please ?

The Following User Says Thank You to clovis86 For This Useful Post:
pycage

Manatus | # 77 | 2014-04-30, 06:44 | Report

Originally Posted by clovis86 View Post

which OC release version did you try with please ?

The version is release 6.0.3 (out yesterday).

I checked this morning that Meedav client on N9 works with it, so it is likely a sabredav induced problem. Unfortunately copypaste does not work from terminal for me, so I have to wait I get Jolla connected to computer for easy logging.

Manatus | # 78 | 2014-04-30, 08:43 | Report

Here is what harbour-cargodock has to say about the issue. This is with proper certificate using official owncloud webdav path

Code:

https://[hostname]/remote.php/webdav/

Code:

create model webdav {d179b16d-05aa-4123-9b26-938529756c1e}
[D] DavModel::loadDirectory:189 - virtual void DavModel::loadDirectory(const QString&) "/" 
[D] DavApi::propfind:135 - void DavApi::propfind(const QString&) "/" 
[D] DavApi::slotPropfindReceived:243 - void DavApi::slotPropfindReceived() 405 "" 
[D] DavApi::slotPropfindReceived:245 - (QPair("Date","Wed, 30 Apr 2014 08:35:17 GMT") ,  QPair("Server","Apache/2.2.15 (Red Hat) PHP/5.4.21 mod_ssl/2.2.15 OpenSSL/1.0.1e-fips") ,  QPair("X-Powered-By","PHP/5.4.21") ,  QPair("Expires","Thu, 19 Nov 1981 08:52:00 GMT") ,  QPair("Cache-Control","no-store, no-cache, must-revalidate, post-check=0, pre-check=0") ,  QPair("Pragma","no-cache") ,  QPair("Strict-Transport-Security","max-age=31536000") ,  QPair("X-XSS-Protection","1; mode=block") ,  QPair("X-Content-Type-Options","nosniff") ,  QPair("X-Frame-Options","Sameorigin") ,  QPair("Content-Security-Policy","default-src 'self'; script-src 'self' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; frame-src *; img-src *; font-src 'self' data:; media-src *") ,  QPair("Set-Cookie","50d09853847b0=9annlf6kr4dgbhohkaroa5ot94; path=/; HttpOnly
50d09853847b0=rd4lc83hu2b93ej9fopdvfiqe1; path=/; secure; HttpOnly
oc_username=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT
oc_token=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT
oc_remember_login=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT
oc_username=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/
oc_token=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/
oc_remember_login=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; path=/") ,  QPair("Status","405 Method Not Allowed") ,  QPair("Content-Length","0") ,  QPair("Connection","close") ,  QPair("Content-Type","text/html; charset=utf-8") )

While testing with Meedav on N9 I noticed that other commonly used path

Code:

https://[hostname]/files/webdav.php

does not work anymore with OC 6 for me. I also tested this with CargoDock without success.

EDIT: This may be caused by hardened Apache configuration my Owncloud runs on. If someone has webdav working with OC and CargoDock, please chime in.

Last edited by Manatus; 2014-04-30 at 09:02.

The Following User Says Thank You to Manatus For This Useful Post:
pycage

Manatus | # 79 | 2014-04-30, 21:13 | Report

I did some additional testing this evening with vanilla setup of Owncloud 6.0.2 + PHP 5.3.x on Ubuntu 12.04 LTS box. Unfortunately that didn't help either. It seemed that this setup didn't get as far as the previous one. To counter lack of real certificate on this setup I also tested with plain http.

Earlier tested setup was Owncloud 6.0.3 + PHP 5.4.x + RHEL6 + proper certificate. With that I had today couple of hours session checking through configurations for possibly conflicting modules, php packages, web server hardening config and virtual directory request commands. Basically anything I was able to found about owncloud webdav problems. None had any effect, and CargoDock still bombed after 405 error.

Server side error and access apache logs showed only one request for PROPFIND verb, which gave out 405. I suspect this is not the reason, as working clients do have these too, and it may be connected to unrelated file locking problems with owncloud.

pycage | # 80 | 2014-05-01, 09:50 | Report

Edit: I got OwnCloud working. See next post.

Originally Posted by Manatus View Post

Server side error and access apache logs showed only one request for PROPFIND verb, which gave out 405. I suspect this is not the reason, as working clients do have these too, and it may be connected to unrelated file locking problems with owncloud.

I looked into this and found that the "405 Method Not Allowed" is coming from the web server. WebDAV uses additional HTTP methods beyond GET, POST, and PUT, and the web server has to be configured to accept them.

For the official owncloud client this probably just doesn't matter because it does not use WebDAV.

https://forum.owncloud.org/viewtopic.php?f=26&t=18287

Last edited by pycage; 2014-05-01 at 10:11.