Log Service APIs are HTTP-based interfaces in the REST style. All Log Service API responses provide a group of public response headers. The detailed definitions are as follows.
|Content-Length||Numeric value||Length of the HTTP response content defined in RFC 2616.|
|Content-MD5||String||MD5 value of the HTTP response content defined in RFC 2616. It is an uppercased string produced after the request body undergoes MD5 computation.|
|Content-Type||String||Type of the HTTP response content defined in RFC 2616. Currently, responses of application/json and application/x-protobuf types are supported by the Log Service server.|
|Date||String||The current time when sent. Currently, the parameter supports only the RFC 822 format, and the GMT standard time is used. The formatted string is as follows: %a, %d %b %Y %H:%M:%S GMT (for example: Mon, 3 Jan 2010 08:33:47 GMT).|
|x-log-requestid||String||Unique ID generated by the server that marks this request. This response header is not related to actual applications. It is mainly used for tracking and investigating problems. For API request failure troubleshooting purpose, you can provide this ID to the Log Service team.|