You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2018/05/03 14:16:00 UTC
[jira] [Resolved] (SLING-7647) Anonymous access to content stopped
working
[ https://issues.apache.org/jira/browse/SLING-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz resolved SLING-7647.
----------------------------------------
Resolution: Fixed
Assignee: Bertrand Delacretaz
As briefly discussed on list, and based on some simple changes that I did for the affected tests, it seems like running tests under {{/content}} is the cleanest way to fix this. Marking this ticket fixed accordingly.
> 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)