HP OneView REST API Reference

REST API Response Headers
stdresphdrs.html[10/17/2013 10:36:09 AM]
HP OneView REST API Reference
REST API Response Headers
Name Usage Description
Etag
Returned on single-
resource
GET/PUT/POST
requests. For multi-
resource
GET/PUT/POST
requests, the ETag for
each resource is
returned in the
response body for that
resource.
etag:<entity-tag>
Determines the "revision" of the resource. Any
changes made to a resource will result in a
new, unique ETag/revision value
This allows clients to determine if the resource
has been modified between REST calls. If the
resource was modified, the Etag will be
different.
The resource ETag value is also used to
validate PUT (modify) requests on resources. If
the client does not provide the most current
ETag in the PUT request (either in the if-match
header, or in the resource body), the PUT
request will fail. This prevents changes made
by one client from overwriting changes made
by a different client.
Cache-
Control
Returned from ALL
requests.
Cache-Control:no-cache
Used to disable interim caching by proxies, etc.
In HP OneView, caching by 3rd-party
components is not supported, since access to
all resources must be controlled via OneView's
proprietary authentication and authorization
mechanisms.
The content returned from a GET operation
may vary, based on the Accept header media
type and interface version. Setting this header
on the response ensures that caches map
responses to the specific Accept header in the
request, and do not erroneously return the
incorrect content (for example, media type or
version) from the cache.
Location
returned from all
"asynchronous"
POST/PUT/DELETE
requests.
Location:<URI>
For asynchronous POST/PUT/DELETE
requests, HTTP status 202 (Accepted) is