Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 05707D42C for ; Wed, 27 Feb 2013 08:17:19 +0000 (UTC) Received: (qmail 41074 invoked by uid 500); 27 Feb 2013 08:17:18 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 40456 invoked by uid 500); 27 Feb 2013 08:17:17 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 40060 invoked by uid 99); 27 Feb 2013 08:17:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Feb 2013 08:17:15 +0000 Date: Wed, 27 Feb 2013 08:17:15 +0000 (UTC) From: "Jean-Marc Borer (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (VFS-428) DavException: (301) Moved Permanently MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/VFS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588112#comment-13588112 ] Jean-Marc Borer commented on VFS-428: ------------------------------------- Not sure HC3 and 4 can coexist: WebdavProvider inherits from HttpProvider. If the latter uses HC4, it will probably break the webdav provider which relies on Jackrabbit which in turn requires HC3. Tricky issue. > DavException: (301) Moved Permanently > -------------------------------------- > > Key: VFS-428 > URL: https://issues.apache.org/jira/browse/VFS-428 > Project: Commons VFS > Issue Type: Bug > Affects Versions: 2.0, 2.1 > Environment: Apache 2.2.22 as Testerver and setted up like http://commons.apache.org/vfs/testserver.html (but changed the 'crypt' password) > Reporter: Robert Kornmesser > Priority: Blocker > Labels: webdav > > Running the WebdavProviderTestCase using mvn -P webdav clean test -Dtest.webdav.uri=webdav://vfsusr:vfstest@localhost/vfstest -Dtest=WebdavProviderTestCase results in > {code}DavException: (301) Moved Permanently > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.645 sec <<< FAILURE! > Results : > Tests in error: > junit.framework.TestSuite@55c9be00(org.apache.commons.vfs2.provider.webdav.test.WebdavProviderTestCase$1): Could not determine the type of file "webdav://vfsusr:****@localhost/vfstest/read-tests". > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 > {code} > The deeper Problem is, that the HttpClient using by VFS does not append a trailing slash and mod_dir of httpd has "DirectorySlash On" per default. So httpd send 301 redirect to the same url with / appended. > I know that for this reason of problematic webdav client apache introduced "redirect-carefully" for some user agents using the "BrowserMatch" directive. So I just tried adding the following into my directive > {code} > BrowserMatch "^Jakarta-Commons-VFS" redirect-carefully > BrowserMatch "^Jakarta Commons-HttpClient/3.0" redirect-carefully > BrowserMatch "^Jakarta Commons-HttpClient/3.1" redirect-carefully > {code} > Its needed to have Jakarta-Commons-VFS *and* Jakarta Commons-HttpClient because of two requests from commons vfs using two different user agents. > But instead of solving the issue, I get for every FileObject.getChildren() call at least one FileObject of type imaginary with the same basename as the parent. Thats not a problem at all (besides that this is totally wrong!) but deleting a parent just dont work anymore, because of an *non-existent* imaginary file inside the dir which cannot be deleted of course. > To cut a long story short, what is the right httpd webdav server config to use 2.0 Release version of VFS? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira