This topic describes the common response headers of Simple Log Service API operations.
Parameters
The Simple Log Service API is a RESTful API based on the HTTP protocol. The following table describes the common response headers of all Simple Log Service API responses.
Header name | Type | Description |
Content-Length | Numeric value | The length of the HTTP response body that is defined in RFC 2616. |
Content-MD5 | String | The MD5 hash value of the HTTP response body that is defined in RFC 2616. The value is an uppercase string that is calculated by using the MD5 algorithm. |
Content-Type | String | The type of the HTTP request body that is defined in RFC 2616. Valid values: application/json and application/x-protobuf. |
Date | String | The time when the request is returned. Only the RFC 822 message format is supported. The GMT time is used. The string is in the following format: %a, %d%b%Y %H:%M:%S GMT, for example, Mon, 3 Jan 2010 08:33:47 GMT. |
x-log-requestid | String | The unique ID of the request. The ID is generated by the server. This response header is irrelevant to applications. It is used to troubleshoot issues. To troubleshoot a failed API request, provide this ID to the technical support team of Simple Log Service. |
Example
HTTP/1.1 200
Server: nginx
Content-Length: 0
Connection: close
Access-Control-Allow-Origin: *
Date: Sun, 27 May 2018 07:43:27 GMT
x-log-requestid: 5B0A619F205DC3F30EDA9322