Webdav problems with cadaver: "Did not find a collection resource."

381 views
Skip to first unread message

Bruno Bzeznik

unread,
Sep 15, 2015, 10:42:01 AM9/15/15
to iRODS-Chat
Hi,

I just installed irods-webdav on a server that is used as a gateway to irods, following and adapting the configuration from http://irods.org/post/how-to-drag-and-drop-access-to-irods-with-webdav
Many thanks for this clear step-by-step doc!

I'm doing my tests with the linux client "cadaver".

It's seems to work, but only if I use the "-t" (tolerant) option of cadaver:

bzizou@bart:~$ cadaver -t http://ciment-grid.ujf-grenoble.fr/irods-webdav/home/bzizou
Ignored error: /irods-webdav/home/bzizou/ not WebDAV-enabled:
Did not find a collection resource.
dav:/irods-webdav/home/bzizou/? ls
Listing collection `/irods-webdav/home/bzizou/': succeeded.
Coll: [...]

If I remove the -t, of course, cadaver exits. But with this option, I'm able to browse, cd and get files.

I noticed only 2 things:
- not all my collections are listed, some are strangely missing, but if I cd into a non-listed one, it works and I can get files from it
- at the connection, I get a 401 on the first OPTIONS query; but it might be normal in the auth process:
129.88.37.23 - - [15/Sep/2015:16:38:08 +0200] "OPTIONS /irods-webdav/home/bzizou/ HTTP/1.1" 401 1198 "-" "cadaver/0.23.3 neon/0.30.1"
129.88.37.23 - - [15/Sep/2015:16:38:08 +0200] "OPTIONS /irods-webdav/home/bzizou/ HTTP/1.1" 200 380 "-" "cadaver/0.23.3 neon/0.30.1"
129.88.37.23 - - [15/Sep/2015:16:38:08 +0200] "PROPFIND /irods-webdav/home/bzizou/ HTTP/1.1" 207 801 "-" "cadaver/0.23.3 neon/0.30.1"

My question is: how to debug this? I couldn't find any relevant informations into the log files of tomcat or apache.

Mike Conway

unread,
Sep 15, 2015, 11:00:09 AM9/15/15
to irod...@googlegroups.com
First question...are you using the 'enterprise' version of Milton, or just building using the 'community'?

Community only supports WebDav level 1, I suspect the 'tolerant' flag is related to this.  DFC, in cooperation with the consortium, is looking to get a license to distribute the 'enterprise' milton libs that support WebDav2 at the moment.  This is my first impression anyhow.  On the listings, usually I first go to ACLs, but at any rate the first thing to check, assuming you are using tomcat, is to tail the catalina.out when doing that listing operations, I'd be interested to see what that yields.

MC
--
--
"iRODS: the Integrated Rule-Oriented Data-management System; A community driven, open source, data grid software solution" https://www.irods.org
 
iROD-Chat: http://groups.google.com/group/iROD-Chat

---
You received this message because you are subscribed to the Google Groups "iRODS-Chat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to irod-chat+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mike Conway Java and Integration Architect - DataNet Federation Consortium GitHub: https://github.com/DICE-UNC LinkedIn: https://www.linkedin.com/pub/mike-conway/5/78a/231

Bruno Bzeznik

unread,
Sep 15, 2015, 11:10:02 AM9/15/15
to iRODS-Chat


Le mardi 15 septembre 2015 17:00:09 UTC+2, Mike Conway a écrit :
First question...are you using the 'enterprise' version of Milton, or just building using the 'community'?

community...
 

Community only supports WebDav level 1, I suspect the 'tolerant' flag is related to this.  DFC, in cooperation with the consortium, is looking to get a license to distribute the 'enterprise' milton libs that support WebDav2 at the moment.  This is my first impression anyhow.  On the listings, usually I first go to ACLs, but at any rate the first thing to check, assuming you are using tomcat, is to tail the catalina.out when doing that listing operations, I'd be interested to see what that yields.

I attached the catalina.out file resulting after a connection and a simple ls using cadaver.
 
catalina.out_

Bruno Bzeznik

unread,
Sep 18, 2015, 3:17:57 AM9/18/15
to iRODS-Chat
Is the "old" irods webdavis interface (https://github.com/nesi/webdavis) still working with irods 4.1?
We used an old snapshot of this solution and was working very well when we were using irods 3.3. Do you think that reverting to it might be a solution for us?

Best regards
Reply all
Reply to author
Forward
0 new messages