[Building Sakai] WebDAV issue in Sakai 2.9.2 - Duplicated relativepath

[Daniel Merino]

FYI, this issue is related with using the latest AnyClient version 
(5.4). Older versions of AnyClient (I have tested 3.0 and 4.1) work fine 
in 2.9.2 after reverting SAK-19592, KNL-1035 and KNL-1050.

Not sure if this could be AnyClient's fault, but I have created a new 
JIRA just in case it is not: https://jira.sakaiproject.org/browse/SAK-24435

Best regards.

El 03/10/2013 14:53, Daniel Merino escribió:
> Hi everybody.
>
> First at all, I'm sorry if this issue has been discussed before in this
> list. Today I return to work after a long break.
>
> After upgrading to Sakai 2.9.2, some of our users are experiencing
> errors in WebDAV connections when uploading resources through AnyClient
> app. We have had issues before with Windows and webDAV, but AnyClient
> had never failed in our previous 2.7.1. In fact, we recommend AnyClient
> to any user with WebDAV issues
>
> It seems that relative path is badly managed somewhere and is
> duplicated, so instead of creating the new folder i.e. in
> /dav/<SITE_ID>/ , AnyClient tries to create it in
> /dav/<SITE_ID>/<SITE_ID>/ and it fails.
>
> I have turned on the log in DavServlet in my 2.9.2 test server and this
> is what it is showing:
>
> 2013-10-03 14:39:19,545 DEBUG http-bio-8082-exec-2
> org.sakaiproject.dav.DavServlet -
> Path=/9be92952-3952-42e0-8f74-52b5f64710f8/
> eTag=1376378790320+/9be92952-3952-42e0-8f74-52b5f64710f8
> 2013-10-03 14:39:19,546 DEBUG http-bio-8082-exec-2
> org.sakaiproject.dav.DavServlet - parserProperties
> href=/dav/9be92952-3952-42e0-8f74-52b5f64710f8/
> 2013-10-03 14:39:19,546 DEBUG http-bio-8082-exec-2
> org.sakaiproject.dav.DavServlet - from:130.206.160.199
> path:/9be92952-3952-42e0-8f74-52b5f64710f8 options:
> 2013-10-03 14:39:19,551 DEBUG http-bio-8082-exec-3
> org.sakaiproject.dav.DavServlet - getRelativePathSAKAI =
> /9be92952-3952-42e0-8f74-52b5f64710f8/9be92952-3952-42e0-8f74-52b5f64710f8/
> 2013-10-03 14:39:19,551 DEBUG http-bio-8082-exec-3
> org.sakaiproject.dav.DavServlet - SAKAIDAV doDispatch [PROPFIND]
> /9be92952-3952-42e0-8f74-52b5f64710f8/9be92952-3952-42e0-8f74-52b5f64710f8/
> 2013-10-03 14:39:19,551 DEBUG http-bio-8082-exec-3
> org.sakaiproject.dav.DavServlet - SAKAIDAV remoteuser = daniel.merino
> 2013-10-03 14:39:19,552 DEBUG http-bio-8082-exec-3
> org.sakaiproject.dav.DavServlet - getRelativePathSAKAI =
> /9be92952-3952-42e0-8f74-52b5f64710f8/9be92952-3952-42e0-8f74-52b5f64710f8/
> 2013-10-03 14:39:19,560 DEBUG http-bio-8082-exec-3
> org.sakaiproject.dav.DavServlet - DirContextSAKAI.lookup - This resource
> does not exist:
> /9be92952-3952-42e0-8f74-52b5f64710f8/9be92952-3952-42e0-8f74-52b5f64710f8
>
> After looking in JIRA the latest changes in Sakai 2.9.3 related to
> webDAV, I have reverted SAK-19592, KNL-1035 and KNL-1050 in my test
> server. This has not solved our issue and I have not found more JIRAs
> that could be causing this problem.
>
> Please, could somebody help me? This is a big headache for us as it is
> failing in our production environment.
>
> I can provide any extra info or access to my test server if you need.
>
> Best regards.

-- 
Daniel Merino Echeverría
daniel.merino at unavarra.es
Gestor de teleformación - Centro Superior de Innovación Educativa.
Tfno: 948-168489 - Universidad Pública de Navarra.
--
Hay cosas más importantes que el dinero. ¡El problema es que son tan 
caras...! (Groucho Marx)