The SignString is generated by Method, Uri, Headers, Body from a HTTP(s) request.
|content_md5||Computed MD5 hash of the request body in uppercase hex format.|
If the request body is empty, set content_md5 to an empty string.
|content_type||Content type string. |
If the request body is empty, set content_type to an empty string.
|date||UTC time in RFC 1123 format.|
Kindly note that the calculated signature is only valid for 3 minutes before or after the datetime indicated in this key.
|Sun, 06 Nov 1994 08:49:37 GMT|
|canonicalized_headers||See below for the specification. |
If no customized header is provided, set canonicalized_headers to an empty string
|canonicalized_resource||Resource Uri, See below for the specification.||/commerce/v1/products|
To generate the canonicalized_headers:
Extract all request headers with the
as-prefix key. Kindly note that the headers with the
as-prefix are not limited to
as-signature-*, but also include other
as-prefixed key such as
Convert all the request header key to lowercase (except the header values case), and sort the headers in ASCII code order.
Remove leading spaces and trailing spaces from the header key and value.
Concatenate each of the header key and value with
:, to form a
Concatenate all header pairs with the new line character (ASCII code
|AS-header2: ThisIsHeader2\nAS-Header1: this-is-header-1||as-header1:this-is-header-1\nas-header2:ThisIsHeader2|
canonicalized_resource is the path of the URL, including the query parameters.
If there is any parameter, it should be appended to the path.
The parameters should be sorted by the ASCII code of the key in ascending order, and parameters with duplicate names should be sorted by the value.
The SignString is constructed by concatenating all the required keys with the new line character (ASCII code
Make sure the string encoding is in