[
https://issues.apache.org/jira/browse/SLING-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612157#comment-16612157
]
Robert Munteanu commented on SLING-7916:
----------------------------------------
[~kwin] - maybe you have an idea about this? With Starter 11-SNAPSHOT I can't
seem to reliably check if a folder exists using the webdav method.
Accessing http://localhost:8080/libs returns
{noformat}
HTTP/1.1 302 Found
Content-Length: 0
Date: Wed, 12 Sep 2018 13:49:26 GMT
Location: http://localhost:8080/libs/
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
{noformat}
Following the redirect to http://localhost:8080/libs/ results in
{noformat}
HTTP/1.1 403 Forbidden
Content-Type: text/html;charset=utf-8
Transfer-Encoding: chunked
{noformat}
So the authentication part is not the problem.
> WebDav deployment method fails to deploy when /libs is not readable
> -------------------------------------------------------------------
>
> Key: SLING-7916
> URL: https://issues.apache.org/jira/browse/SLING-7916
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Maven Sling Plugin 2.3.10
>
>
> I created a Sling module using the {{sling-jcrinstall-bundle-archetype}}.
> Deployment using the {{maven-sling-plugin}} fails, with the following message:
> {noformat}Installation on http://localhost:8080/libs/sling/install failed,
> cause: Could not find any intermediate path up until the root of
> http://localhost:8080/libs/sling/install.{noformat}
> At least {{/libs}} is there, so that message is incorrect. Verifying the
> Sling request log I see that redirects sent from Sling are followed using the
> {{anonymous}} user:
> {noformat}127.0.0.1 - admin 12/Sep/2018:15:14:48 +0200 "PUT
> /libs/sling/install/bundle-test-002-1.0-SNAPSHOT.jar HTTP/1.1" 409 2455 "-"
> "Jakarta Commons-HttpClient/3.1"
> 127.0.0.1 - admin 12/Sep/2018:15:14:48 +0200 "HEAD /libs/sling/install
> HTTP/1.1" 404 2524 "-" "Jakarta Commons-HttpClient/3.1"
> 127.0.0.1 - admin 12/Sep/2018:15:14:48 +0200 "HEAD /libs/sling HTTP/1.1" 302
> - "-" "Jakarta Commons-HttpClient/3.1"
> 127.0.0.1 - anonymous 12/Sep/2018:15:14:48 +0200 "HEAD /libs/sling/ HTTP/1.1"
> 404 2461 "-" "Jakarta Commons-HttpClient/3.1"
> 127.0.0.1 - admin 12/Sep/2018:15:14:48 +0200 "HEAD /libs HTTP/1.1" 302 - "-"
> "Jakarta Commons-HttpClient/3.1"
> 127.0.0.1 - anonymous 12/Sep/2018:15:14:48 +0200 "HEAD /libs/ HTTP/1.1" 404
> 2407 "-" "Jakarta Commons-HttpClient/3.1"
> {noformat}
> This is wrong, and we should always be accessing the repository using the
> configured user and password.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
