[ 
https://issues.apache.org/jira/browse/JCRVLT-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886704#comment-16886704
 ] 

Tobias Bocanegra commented on JCRVLT-341:
-----------------------------------------

I guess the problem is in spi2dav, then:

[https://github.com/apache/jackrabbit/blob/48e725ca1931e972fd6bde3902db85b9769e7011/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2dav/RepositoryServiceImpl.java#L331]

/cc [~reschke]

 

> https doesn't work anymore
> --------------------------
>
>                 Key: JCRVLT-341
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-341
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: RCP, vlt
>    Affects Versions: 3.1.44, 3.2.6, 3.2.8
>         Environment: source instance is suse linux sles 12
> target instance is suse linux sles 12 and windows 10
> java 1.8
> AEM 6.4.4
>            Reporter: WalterSteiner
>            Priority: Major
>
> org.apache.jackrabbit.vault.rcp-3.1.24 introduced support of https. I now 
> upgraded to the version 3.2.8. I want to transfer with the following path 
> "/content/etc/robots.txt"  from one aem-author instance to another. I get the 
> following log entry
> 16.07.2019 10:52:52.827 *ERROR* [Vault RCP Task - copy-contentetcrobots.txt] 
> org.apache.jackrabbit.vault.util.RepositoryCopier Error while retrieving src 
> node /content/etc/robots.txt: javax.jcr.PathNotFoundException: 
> /content/etc/robots.txt
> In the source, this path exists. If I do the same with http. The path is 
> found and the content transfered.
> I use the following json to create the tast in aem
> {code}
> {
>  "cmd":"create",
>  "id":"copy-contentetcrobots.txt",
>  
> "src":"https://user:password@host:port/crx/server/crx.default/jcr:root/content/etc/robots.txt";,
>  "dst":"/content/etc/robots.txt",
>  "batchsize": 2048,
>  "update": true,
>  "onlyNewer": true,
>  "recursive": true,
>  "throttle": 1,
>  "excludes": []
> }
> {code}
> Please fix this issue, because we are no longer allowed to use http in our 
> company.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to