iDRAC8 with Lifecycle Controller Version 2.70.70.70 Redfish API Guide

HTTP headers

The server response contains only basic information about related resources. Any metadata that is required to process a request or response is accessed by using HTTP headers. iDRAC supports the following request headers:

Header

Description

If-Match

Supported only for AccountService and FirmwareInventory URIs.

If-None-Match

Supported only for AccountService, FirmwareInventory, and metadata URIs.

Content-Length

Returned on all responses except responses that have Transfer-Encoding: chunked.

Content-Type

• Responses other than OData metadata—application/json;charset=utf-8
• OData responses—application/xml;charset=utf-8

ETag

Supported on AccountService, FirmwareInventory, and metadata URIs.

Location

Service sets this header when resources are created or when HTTP requests are redirected to other resources.

Cache-Control

Returned on all responses. Metadata URIs support cached responses. Instrumentation resources cannot be cached.

X-Auth-Token

Used for authentication of user sessions. See “Session-based authentication” under Redfish authentication and authorization.