-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.1.0 CE GA1, 6.2.0 CE M2
-
Fix Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2, 6.2.0 CE M2
-
Component/s: Documents & Media, WebDAV access
-
Labels:
-
Branch Version/s:6.1.x
-
Backported to Branch:Committed
-
Git Pull Request:
Steps to reproduce :
1) As an administrator create a community called test
2) Change the friendly url of the test community to /test1 (it will be /test by default)
3) Add a document library portlet to the test community
4) Upload a document called Doc1.doc
5) Go to the file details and copy and paste the webdav url in another browser window (eg. : http://localhost:8080/tunnel-web/secure/webdav/test1/document_library/Doc1.doc) You should be able to download this file
6) As an administrator create another group called test1
7) Open the webdav url from step 5 again and try to download the document. You will not be able to
The problem is depending on your viewpoint in the getGroupId method of com.liferay.portal.kernel.webdav.WebDAVUtil or in view_file_entry.jsp
Basically if the url is http://localhost:8080/tunnel-web/secure/webdav/test1/...
It will first check if test1 is a groupname. If this is the case it will look for the file in that group. Only when it finds no group that has a matching name will it look at the friendly url
Unfortunately view_file_entry.jsp uses the friendly url path in the url, never the name
- relates
-
LPE-6174 WebDAV does not work if there is a group name set to the friendly URL of another group
-
- Closed
-