This topic describes the common response headers of Log Service API operations.
Log Service API operations are RESTful API operations that are based on the HTTP protocol. The following table describes the common response headers of all Log Service API responses.
|Content-Length||Numeric value||The length of the HTTP response body that is defined in RFC 2616.|
|Content-MD5||String||The MD5 digest of the HTTP response body that is defined in RFC 2616. The string that is generated after the response body is calculated based on the MD5 algorithm. The value is in uppercase.|
|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 that marks the request. The ID is generated by Log Service. This response header is irrelevant to applications. It is used to troubleshoot problems. To troubleshoot a failed API request, provide this ID to the technical support team of Log Service.|
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