sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anisha Narang (Jira)" <>
Subject [jira] [Created] (SLING-8974) Shows a 200 OK for a delete operation even if the node does not exist.
Date Wed, 08 Jan 2020 19:28:00 GMT
Anisha Narang created SLING-8974:

             Summary: Shows a 200 OK for a delete operation even if the node does not exist.
                 Key: SLING-8974
             Project: Sling
          Issue Type: Bug
          Components: Sling Query
            Reporter: Anisha Narang

When you try any curl query for a 'delete' operation, it shows a 200 OK even even the node
does not exist.

curl query:
$ curl -F":operation=delete"

    <title>Content modified /content/invalid_node</title>
    <h1>Content modified /content/invalid_node</h1>
                <td><div id="Status">200</div></td>
                <td><div id="Message">OK</div></td>
                <td><a href="/invalid_node" id="Location">/invalid_node</a></td>
                <td>Parent Location</td>
                <td><a href="/content" id="ParentLocation">/content</a></td>
                <td><div id="Path">/content/invalid_node</div></td>
                <td><div id="Referer"></div></td>
                <td><div id="ChangeLog">&lt;pre&gt;deleted(&quot;/content/invalid_node&quot;);&lt;br/&gt;&lt;/pre&gt;</div></td>
    <p><a href="/invalid_node">Modified Resource</a></p>
    <p><a href="/content">Parent of Modified Resource</a></p>
So, even though this node does not exist, there is a 200 OK response for the same which is
not expected as per the documentation here -> []

Expected result:

The response should be 404 not found if the not does not exist.

This message was sent by Atlassian Jira

View raw message