3.1.4.5.1 Common Rules for Sending Delete Requests

This section defines all the rules to which clients MUST adhere when sending Delete requests. Therefore, no additional rules for specific Delete request types are defined in this document.

Delete requests MUST adhere to the syntax rules specified in Delete Request Types (section 2.2.7.4).

If the delete request URI (provided by the higher layer) identifies an EntityType instance for a type that has a concurrency token defined, then the client SHOULD include an If-Match (section 2.2.5.5) header in the request. The concurrency token provided as the value of the If-Match header MUST be a token associated with the EntityType of the entity identified by the request URI. DeleteLink requests MUST NOT include an If-Match (section 2.2.5.5).

Use of the If-None-Match request header with Delete request types is not defined in this document.

If the data service identified by the request URI supports tunneled requests, then any of the Delete Request Types (section 2.2.7.4) MAY be sent as a tunneled request (section 2.2.7.7).

Rules for processing the response to Delete Requests is specified in Common Rules for Receiving Responses from Data Service Requests (section 3.1.5.1).