You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2013/08/20 02:16:52 UTC
[jira] [Resolved] (JCR-3650) vlt: DavException when checkout
against jackrabbit standalone
[ https://issues.apache.org/jira/browse/JCR-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Bocanegra resolved JCR-3650.
-----------------------------------
Resolution: Fixed
Added new davex option: 'referer'.
Example to issue the davex requests with an empty referer:
vlt -Xdavex:referer= --credentials admin:admin co --force http://localhost:8080/server/default/jcr:root/ .
--
Committed revision 1515677.
> vlt: DavException when checkout against jackrabbit standalone
> -------------------------------------------------------------
>
> Key: JCR-3650
> URL: https://issues.apache.org/jira/browse/JCR-3650
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
>
> Trying to checkout against jackrabbit standalone produces:
> $ vlt --credentials admin:admin co --force http://localhost:8080/server/default/jcr:root/ .
> Checkout http://localhost:8080/server/default/jcr:root/ with local files using root at /Users/tripod/tmp/vlttest/co/jcr_root
> Connecting via JCR remoting to http://localhost:8080/server
> [ERROR] checkout: org.apache.jackrabbit.vault.vlt.VltException: Unable to mount filesystem
> caused by: javax.jcr.RepositoryException: unknown protocol: about
> caused by: org.apache.jackrabbit.webdav.DavException: unknown protocol: about
> And the jetty.log shows:
> 2013-08-19 16:21:47.408 WARN [1788647656@qtp-1788255273-6] Slf4jLog.java:76 /server/: java.net.MalformedURLException: unknown protocol: about
> This is caused by a referrer header that is set to "about:blank" in order to circumvent empty-referrer header checks in other servers. I suggest to make this configurable, and default to "http://localhost/"
--
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