[
https://issues.apache.org/jira/browse/SLING-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-8186.
----------------------------------------
Resolution: Won't Fix
I have added a note about this behavior at [1], should be live soon, [website
commit
ae899929|https://github.com/apache/sling-site/commit/ae899929f170864832cbbf621bea61ca1a3423f8].
Marking this issue won't fix, as discussed there doesn't seem to be a simple
way of eliminating this behavior while remaining backwards compatible.
[1]
https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html
> Moved node is deleted if @Delete parameter points to its name
> -------------------------------------------------------------
>
> Key: SLING-8186
> URL: https://issues.apache.org/jira/browse/SLING-8186
> Project: Sling
> Issue Type: Bug
> Components: Servlets
> Affects Versions: Servlets Post 2.3.26
> Reporter: Burkhard Pauli
> Assignee: Bertrand Delacretaz
> Priority: Major
> Attachments: patch.diff
>
>
> If a file is moved to a new location with the @MoveFrom parameter and the
> request contains the @Delete parameter at the same time, the file is dropped
> and never saved to the new location.
> Step to reproduce the issue:
> # Create a node of type nt:file at the location {{/content/file}}
> # Execute the following curl command:
> {{curl -u admin:admin -F './test/title=Hello World' -F
> './test/file@MoveFrom=/content/file' -F './test@Delete=true'
> [http://localhost:4502/content]}}
> Observed behaviour:
> The file is not saved at the new location at {{/content/test/file}} and it
> is not available anymore at the old location {{/content/file}}
> Expected:
> The file is saved at the new location {{/content/test/file}} as long as
> other properties are saved when the request contains the delete operation
> (like the title property in the example above).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
