2.2.1.3.4 ETag

This is a common response header that contains an opaque string representing the state of the resource at the time the response was generated. This header is returned for requests that target a single entity. The Network Controller will also always return an etag in the response body, as the etag property of an entity.

If the request does not include an If-Match request header, then the Network Controller returns an error response code. Other status codes that are associated with the etag header are as follows.

Status code	Description
200 (OK)	Operation completed successfully.
201 (Created)	Resource completed successfully.
204 (No Content)	Resource to delete does not exist
412 (Precondition Failed)	Parent resource is unavailable
404 (Not Found)	Resource was not found.