You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Robert Kornmesser (JIRA)" <ji...@apache.org> on 2012/07/16 17:44:35 UTC
[jira] [Updated] (VFS-428) DavException: (301) Moved Permanently
[ https://issues.apache.org/jira/browse/VFS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Kornmesser updated VFS-428:
----------------------------------
Description:
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 <Directory> 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?
was:
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://korni.gfz-potsdam.de/webdav/rz/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 <Directory> 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?
> 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 <Directory> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira