[
https://issues.apache.org/jira/browse/SLING-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462660#comment-16462660
]
Bertrand Delacretaz commented on SLING-7647:
--------------------------------------------
...and later I found out that {{/content}} can be troublesome as there's a
resource resolver mapping on that path by default, meaning that a POST to
create a node under {{/content}} might return a URL that's mapped to omit
{{/content}}. As the tests that we are talking about as mostly old ones that we
don't want to touch more than strictly needed,
To fix this I'm creating an {{/ANON_CAN_READ}} path in the repoinit setup of
the launchpad-testing module, that can be used for the few tests that need
anonymous access and are not convenient to run under {{/content}}.
> Anonymous access to content stopped working
> -------------------------------------------
>
> Key: SLING-7647
> URL: https://issues.apache.org/jira/browse/SLING-7647
> Project: Sling
> Issue Type: Bug
> Components: Authentication
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Major
> Labels: sling-IT
> Attachments: sling10-get-request.txt, trunk-get-request.txt
>
>
> Looking at SLING-7636 and especially the {{AnonymousAccessTest}} shows that
> anonymous access stopped working. The following scenario works with the
> sling10 jar but not with the current trunk:
> {code}
> curl -u admin:admin -Ftitle=test http://localhost:8080/tmp/test1234
> curl -u admin:admin http://localhost:8080/tmp/test1234.json
> curl http://localhost:8080/tmp/test1234.tidy.json
> {code}
> With sling10 the last request gets content, while with the current trunk it
> gets a 404.
> I'll attach the logs of that last request on both versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
