Requests for deleted resources
Issue
Since DestinationData adopts RESTfull API style, each resource is available through its own URL, such as "https://www.example.com/2022-04/agents/1"
. Clients of a server may rely on these URLs for long periods of time allowing for situations where requests can be made to resources that have been deleted.
Currently the standard states that servers MUST respond to requests for deleted resource with the error status 410 Gone
, but members have raised the issue that traceability of deleted resources is a sophisticated feature that should not be required.
Proposal
The members in the most recent meeting have discussed towards allowing server to NOT implement traceability of deleted resources, in which case requests for such resources should with the error status code 404 Not Found
.