[
https://issues.apache.org/jira/browse/SLING-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617782#action_12617782
]
Lars Trieloff commented on SLING-588:
-------------------------------------
I think you are wrong here. In order to get content from the JCR node
/some/sample.html I will send a GET request to /some/sample.html or
/some/sample.html.html (or any other combination of selectors and extensions).
Sling is right to detect extensions and selectors after (!) having found the
content.
Dealing with POST requests ignores extensions and selectors completely (I
cannot have a POST.html.esp, for instance) so I expect that posting to an URL
will not consider extensions and selectors. This works fine for existing
resources (I POST to /some/sample.html or /some/sample.html.foobar and it will
update the node /some/sample.html) but it breaks the behavior for non-existing
resources.
Sling is trying to be smarter than the user here by expecting that no
reasonable person could ever want to create a node with a dot in its name.
> Sling ignores specified node path when creating content
> -------------------------------------------------------
>
> Key: SLING-588
> URL: https://issues.apache.org/jira/browse/SLING-588
> Project: Sling
> Issue Type: Bug
> Reporter: Lars Trieloff
> Attachments: SLING-588.patch
>
>
> As described here: http://markmail.org/message/u3be3mpaal4efngj Sling will
> ignore the node path specified in the HTTP request when creating contents
> which makes it impossible to create nodes with a dot in the node name from a
> form post.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
