[SLING-3203] Post servlet's delete operation deletes parent of nonexisting node

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Servlets Post 2.3.2
• Fix Version/s: Servlets Post 2.3.4
• Component/s: Servlets
• Assignee: Bertrand Delacretaz
• Reporter: Bertrand Delacretaz
• Created: 23/Oct/13 12:18
• Updated: 27/Mar/14 13:17
• Resolved: 22/Jan/14 13:12

Description

In the below scenario, /tmp/test is gone after the delete operation - the resource resolver goes up the path of the nonexisting node, and it's /tmp/test that's provided to the DeleteOperation.

I think we should change this (maybe with a backwards compatibility switch), as it's clear that the user's intention in this case is not to delete /tmp/test. Maybe just reject :delete operations if the request has any selector or extensions.

curl -u admin:admin -X POST http://localhost:8080/tmp/test/some.node
curl -u admin:admin http://localhost:8080/tmp/test.tidy.2.json # looks good
curl -u admin:admin -F:operation=delete http://localhost:8080/tmp/test.other/nothing
curl -u admin:admin http://localhost:8080/tmp/test.tidy.2.json # 404