[
https://issues.apache.org/jira/browse/SLING-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-7651.
----------------------------------------
Resolution: Fixed
Turns out this was caused by an {{/etc/map}} mapping for localhost (!) from the
starter-content module.
[~klcodanr] could you review my changes from this commit?
https://github.com/apache/sling-org-apache-sling-starter-content/commit/268299d1a18184c568fe99db63a93622f6929a66
I have removed the mapping on localhost...it feels weird to have such a
specific mapping in our default config, maybe that was an oversight or leftover
from some tests?
Anyway, with that mapping removed all is good and I could revert the unwanted
{{PostToRootTest}} changes of SLING-7636.
> POST to / creates nodes instead of setting properties
> -----------------------------------------------------
>
> Key: SLING-7651
> URL: https://issues.apache.org/jira/browse/SLING-7651
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Post 2.3.24
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Major
>
> The changes that I had to make to {{PostToRootTest}} [1] indicate that the
> POST behavior has changed since sling10, at least on /.
> With sling10 this request sets a property {{x=y }}on the root node, while
> with the current trunk it creates a node under the root.
> {code:java}
> curl -u admin:admin -Fx=y http://localhost:8080/
> {code}
> It looks like the culprit is {{resource}} being null in
> {{AbstractCreateOperation.processCreate}}, in this code:
> {code:java}
> final String path = response.getPath();
> final Resource resource = resolver.getResource(path);
> {code}
> I'll investigate further - and the changes to {{PostToRootTest}} should be
> reverted once this is fixed.
> [1]
> [https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/commit/3750eb05dc038544ba155d91de8991114077ac0c]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
