You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hoping we can change the delete() contract to allow for sending status entities back on bulk DELETE operations. Per RFC:
RFC2616 9.7 DELETE: "A successful response SHOULD be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted, or 204 (No Content) if the action has been enacted but the response does not include an entity.”
I’m wondering, could we have the restful plugin support both codes according to the standard? Meaning, could we support void delete(…) and def delete(…). Right now, I’m struggling to support a bulk DELETE operation without sending back a content body describing the status of each individual delete operation in the bulk request.
The text was updated successfully, but these errors were encountered:
Hoping we can change the delete() contract to allow for sending status entities back on bulk DELETE operations. Per RFC:
RFC2616 9.7 DELETE: "A successful response SHOULD be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted, or 204 (No Content) if the action has been enacted but the response does not include an entity.”
I’m wondering, could we have the restful plugin support both codes according to the standard? Meaning, could we support void delete(…) and def delete(…). Right now, I’m struggling to support a bulk DELETE operation without sending back a content body describing the status of each individual delete operation in the bulk request.
The text was updated successfully, but these errors were encountered: