Common request headers

    Heading Description
    Authorization Any request to Yandex Object Storage must be authorized.

    This header must be used with either the Date or x-amz-date header.

    Learn about authorization methods in the corresponding sections of the guide.
    Cache-Control A set of directives for caching data according to RFC 2616.
    Content-Disposition The name Object Storage suggests saving an object as a file under when it's downloaded. Compliant with RFC 2616.
    Content-Encoding Defines content encoding according to RFC 2616.
    Content-Length Length of the request body (without headers) in compliance with RFC 2616.

    This header is required for all requests that send data to Object Storage (such as when uploading an object).
    Content-Type Data type in a request. For example, text/plain.

    The default value is binary/octet-stream.
    Content-MD5 128-bit MD5 hash value of the request body, base64 encoded.

    Compliant with RFC 1864.

    Object Storage uses this header to verify that the data sent matches the data received.
    Date The date and time a request is sent.

    Format: Thu, 18 Jan 2018 09:57:35 GMT.

    When x-amz-date is set, Object Storage ignores the Date header.
    Expect The expected code is 100 Continue.

    When uploading data to Object Storage, an app can use the following logic:
    - Send a request without a body, but with the Expect: 100-continue header set.
    - Send a request with a body after getting the 100-continue response. This request must not have the Expect header.
    Expires Response expiration date. Complaint with RFC 2616.
    Host Request recipient host.

    This header is required for HTTP/1.1, but optional for HTTP/1.0 requests.
    x-amz-date The date and time at the request source.

    Format: Thu, 18 Jan 2018 09:57:35 GMT.

    When x-amz-date is set, Object Storage ignores the Date header.

    If a cross-domain (CORS) request is sent, it may contain the headers of the options preflight request.