额外的 HTTP headers 会影响 MWS Feed API 提交吗?
Can extra HTTP headers influence on MWS Feed API submission?
调试亚马逊 MWS Feed 提交是令人讨厌的,因为无论您做错了什么,Ama 都只是 returns 相同的毫无意义的错误消息:
<Error>
<Type>Sender</Type>
<Code>InvalidParameterValue</Code>
<Message>Either Action or Operation query parameter must be present.</Message>
</Error>
我 100% 肯定我正确地构建了 StringToSign 并计算了 HMAC-SHA256 等。我花了几周的时间收集并采用了一堆有用的函数来进行哈希、签名、base64ing 等。MWS要求。用纯 Pascal 编写,它们都在订单和产品 APIs.
上进行了测试
现在说到 Feeds API 我被上面的错误困住了。所有参数都与 MWS Scratchpad 生成的参数相同。我测试了 MWS Scratchpad 生成的提交 StringToSign,但没有成功。
到目前为止我注意到的是:MWS Scratchpad 生成的 header 和我的应用程序生成的 number/values 之间存在差异。
Scratchpad 生成以下 headers(至少它们被显示):
Host: mws.amazonservices.ca
x-amazon-user-agent: AmazonJavascriptScratchpad/1.0 (Language=Javascript)
Content-Type: text/xml
我的应用程序使用 Indy(在 XE4 中)TIdHTTP 发出请求。当亚马逊returns出现以上错误时,Request.RawHeaders.Text
包含以下内容:
Content-Length: 251
x-amazon-user-agent: MyApp/1.1(Language=Delphi;Platform=Windows7)
Content-Type: text/xml
Host: mws.amazonservices.ca
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: identity
User-Agent: MyApp/1.1(Language=Delphi;Platform=Windows7)
看起来额外的 header 默认添加到 Request
object。我的第一个问题是:这些额外的 header 理论上会影响行为吗? IE。他们能成为表演者吗?
我的第二个问题:是否有任何选项可以修改 Indy 中的默认标题列表 HTTP.Request
?要继续调试,我宁愿排除额外的 headers 以查看请求是否有效。
更新: (SignedString)
AWSAccessKeyId=<AWSAccessKeyId>
&Action=GetFeedSubmissionList
&Merchant=<MerchantId>
&SignatureMethod=HmacSHA256
&SignatureVersion=2
&Timestamp=2015-07-26T09%3A04%3A59Z
&Version=2009-01-01
&Signature=1OI0PVgL3uh5sFXxjCzaaWEwGmW6h5e0dgLUFkPgoXg%3D
更新:(完整的 HTTP Request/Response 由 TIdLogFile
提供)
Stat Connected.
Sent 28.07.2015 12:28:11:
POST / HTTP/1.1<EOL>
Content-Type: text/xml; charset=us-ascii<EOL>
Content-Length: 279<EOL>
x-amazon-user-agent: MyAppNameAndVer<EOL>
Host: mws.amazonservices.ca<EOL>
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8<EOL>
Accept-Encoding: identity<EOL>
User-Agent: Mozilla/3.0 (compatible; Indy Library)<EOL><EOL>
Sent 28.07.2015 12:28:11:
AWSAccessKeyId=<AWSAccessKeyId>
&Action=GetFeedSubmissionList
&MWSAuthToken=<AWSAuthToken>
&Merchant=<MerchantId>
&SignatureMethod=HmacSHA256
&SignatureVersion=2
&Timestamp=2015-07-28T10%3A28%3A09Z
&Version=2009-01-01
&Signature=I6euLIiVDzjZ8bbdtF840K0TJCkGh4NrUbQPtQtu78A%3D
Recv 28.07.2015 12:28:11:
HTTP/1.1 400 Bad Request<EOL>
Date: Tue, 28 Jul 2015 10:28:10 GMT<EOL>
Server: AmazonMWS<EOL>
x-mws-request-id: 7e63280d-1db5-4d10-af40-587747d032a8<EOL>
x-mws-timestamp: 2015-07-28T10:28:11.048Z<EOL>
x-mws-response-context: OmAlguEmW20QT07uIdb9d25xkX+JSS7uFr1rDvXIoqXMvbUFzUMt1b5Xl2WzDaJszbwr25N/J4c=<EOL>
Content-Type: text/xml<EOL>
Content-Length: 324<EOL>
Vary: User-Agent<EOL>
nnCoection: close<EOL><EOL>
<?xml version="1.0"?><LF><ErrorResponse xmlns="https://mws.amazonservices.com/"><LF> <Error><LF> <Type>Sender</Type><LF> <Code>InvalidParameterValue</Code><LF> <Message>Either Action or Operation query parameter must be present.</Message><LF> </Error><LF> <RequestID>7e63280d-1db5-4d10-af40-587747d032a8</RequestID><LF></ErrorResponse><LF>
Stat Disconnected.
请注意:为了方便您在 <EOL>
之后添加 CR,我对回复进行了格式化
混淆 nnCoection
header 解释如下:
我的问题现在已经解决了。以下是我感谢没有违反社区标准的人的方式;-)
Days := 1;
repeat
IsSuccessful := DebugAmazonFeedSubmissionProc;
Inc(Days);
until IsSuccessful or (Days = 14);
if not IsSuccessful then
begin
AskTheGods(@Whosebug);
Sleep(1000); // ...wake up and drink a cup'o'tea :)
Expert := TRemyLebeau.Create('delphi');
try
Expert.ReviewTheCode;
Expert.GetTheJobDone;
finally
// You may dispose the instance here,
// but the Class is one of the most valuable assets of the Community.
// Thank you, Remy!
end;
end;
您的请求Content-Type
header是错误的。您已将其设置为 text/xml; charset=us-ascii
,但您实际上并没有发送 XML 数据。根据 MWS GetFeedSubmissionList 文档,您需要将 Content-Type
(通过 TIdHTTP.Request.ContentType
属性)设置为 application/x-www-form-urlencoded
。
TIdHTTP.Post()
的 TStrings
版本将为您设置 ContentType
,但您使用的是 TStream
版本,因此您必须设置 ContentType
手动。在这种情况下,我建议您切换到 TStrings
版本,让它为您处理表单字段的编码:
var
PostData: TStringList;
begin
PostData := TStringList.Create;
try
PostData.Add('AWSAccessKeyId=<AWSAccessKeyId>');
PostData.Add('Action=GetFeedSubmissionList');
PostData.Add('MWSAuthToken=<AWSAuthToken>');
PostData.Add('Merchant=<MerchantId>');
PostData.Add('SignatureMethod=HmacSHA256');
PostData.Add('SignatureVersion=2');
PostData.Add('Timestamp=2015-07-28T10:28:09Z'); // <-- NOT percent encoded yet!
PostData.Add('Version=2009-01-01');
PostData.Add('Signature=I6euLIiVDzjZ8bbdtF840K0TJCkGh4NrUbQPtQtu78A='); // <-- NOT percent encoded yet!
IdHTTP1.Request.CustomHeaders.Values['x-amazon-user-agent'] := 'MyAppNameAndVer';
IdHTTP1.Post('http://mws.amazonservices.ca', PostData);
finally
PostData.Free;
end;
end;
调试亚马逊 MWS Feed 提交是令人讨厌的,因为无论您做错了什么,Ama 都只是 returns 相同的毫无意义的错误消息:
<Error>
<Type>Sender</Type>
<Code>InvalidParameterValue</Code>
<Message>Either Action or Operation query parameter must be present.</Message>
</Error>
我 100% 肯定我正确地构建了 StringToSign 并计算了 HMAC-SHA256 等。我花了几周的时间收集并采用了一堆有用的函数来进行哈希、签名、base64ing 等。MWS要求。用纯 Pascal 编写,它们都在订单和产品 APIs.
上进行了测试现在说到 Feeds API 我被上面的错误困住了。所有参数都与 MWS Scratchpad 生成的参数相同。我测试了 MWS Scratchpad 生成的提交 StringToSign,但没有成功。
到目前为止我注意到的是:MWS Scratchpad 生成的 header 和我的应用程序生成的 number/values 之间存在差异。
Scratchpad 生成以下 headers(至少它们被显示):
Host: mws.amazonservices.ca
x-amazon-user-agent: AmazonJavascriptScratchpad/1.0 (Language=Javascript)
Content-Type: text/xml
我的应用程序使用 Indy(在 XE4 中)TIdHTTP 发出请求。当亚马逊returns出现以上错误时,Request.RawHeaders.Text
包含以下内容:
Content-Length: 251
x-amazon-user-agent: MyApp/1.1(Language=Delphi;Platform=Windows7)
Content-Type: text/xml
Host: mws.amazonservices.ca
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: identity
User-Agent: MyApp/1.1(Language=Delphi;Platform=Windows7)
看起来额外的 header 默认添加到 Request
object。我的第一个问题是:这些额外的 header 理论上会影响行为吗? IE。他们能成为表演者吗?
我的第二个问题:是否有任何选项可以修改 Indy 中的默认标题列表 HTTP.Request
?要继续调试,我宁愿排除额外的 headers 以查看请求是否有效。
更新: (SignedString)
AWSAccessKeyId=<AWSAccessKeyId>
&Action=GetFeedSubmissionList
&Merchant=<MerchantId>
&SignatureMethod=HmacSHA256
&SignatureVersion=2
&Timestamp=2015-07-26T09%3A04%3A59Z
&Version=2009-01-01
&Signature=1OI0PVgL3uh5sFXxjCzaaWEwGmW6h5e0dgLUFkPgoXg%3D
更新:(完整的 HTTP Request/Response 由 TIdLogFile
提供)
Stat Connected.
Sent 28.07.2015 12:28:11:
POST / HTTP/1.1<EOL>
Content-Type: text/xml; charset=us-ascii<EOL>
Content-Length: 279<EOL>
x-amazon-user-agent: MyAppNameAndVer<EOL>
Host: mws.amazonservices.ca<EOL>
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8<EOL>
Accept-Encoding: identity<EOL>
User-Agent: Mozilla/3.0 (compatible; Indy Library)<EOL><EOL>
Sent 28.07.2015 12:28:11:
AWSAccessKeyId=<AWSAccessKeyId>
&Action=GetFeedSubmissionList
&MWSAuthToken=<AWSAuthToken>
&Merchant=<MerchantId>
&SignatureMethod=HmacSHA256
&SignatureVersion=2
&Timestamp=2015-07-28T10%3A28%3A09Z
&Version=2009-01-01
&Signature=I6euLIiVDzjZ8bbdtF840K0TJCkGh4NrUbQPtQtu78A%3D
Recv 28.07.2015 12:28:11:
HTTP/1.1 400 Bad Request<EOL>
Date: Tue, 28 Jul 2015 10:28:10 GMT<EOL>
Server: AmazonMWS<EOL>
x-mws-request-id: 7e63280d-1db5-4d10-af40-587747d032a8<EOL>
x-mws-timestamp: 2015-07-28T10:28:11.048Z<EOL>
x-mws-response-context: OmAlguEmW20QT07uIdb9d25xkX+JSS7uFr1rDvXIoqXMvbUFzUMt1b5Xl2WzDaJszbwr25N/J4c=<EOL>
Content-Type: text/xml<EOL>
Content-Length: 324<EOL>
Vary: User-Agent<EOL>
nnCoection: close<EOL><EOL>
<?xml version="1.0"?><LF><ErrorResponse xmlns="https://mws.amazonservices.com/"><LF> <Error><LF> <Type>Sender</Type><LF> <Code>InvalidParameterValue</Code><LF> <Message>Either Action or Operation query parameter must be present.</Message><LF> </Error><LF> <RequestID>7e63280d-1db5-4d10-af40-587747d032a8</RequestID><LF></ErrorResponse><LF>
Stat Disconnected.
请注意:为了方便您在 <EOL>
混淆 nnCoection
header 解释如下:
我的问题现在已经解决了。以下是我感谢没有违反社区标准的人的方式;-)
Days := 1;
repeat
IsSuccessful := DebugAmazonFeedSubmissionProc;
Inc(Days);
until IsSuccessful or (Days = 14);
if not IsSuccessful then
begin
AskTheGods(@Whosebug);
Sleep(1000); // ...wake up and drink a cup'o'tea :)
Expert := TRemyLebeau.Create('delphi');
try
Expert.ReviewTheCode;
Expert.GetTheJobDone;
finally
// You may dispose the instance here,
// but the Class is one of the most valuable assets of the Community.
// Thank you, Remy!
end;
end;
您的请求Content-Type
header是错误的。您已将其设置为 text/xml; charset=us-ascii
,但您实际上并没有发送 XML 数据。根据 MWS GetFeedSubmissionList 文档,您需要将 Content-Type
(通过 TIdHTTP.Request.ContentType
属性)设置为 application/x-www-form-urlencoded
。
TIdHTTP.Post()
的 TStrings
版本将为您设置 ContentType
,但您使用的是 TStream
版本,因此您必须设置 ContentType
手动。在这种情况下,我建议您切换到 TStrings
版本,让它为您处理表单字段的编码:
var
PostData: TStringList;
begin
PostData := TStringList.Create;
try
PostData.Add('AWSAccessKeyId=<AWSAccessKeyId>');
PostData.Add('Action=GetFeedSubmissionList');
PostData.Add('MWSAuthToken=<AWSAuthToken>');
PostData.Add('Merchant=<MerchantId>');
PostData.Add('SignatureMethod=HmacSHA256');
PostData.Add('SignatureVersion=2');
PostData.Add('Timestamp=2015-07-28T10:28:09Z'); // <-- NOT percent encoded yet!
PostData.Add('Version=2009-01-01');
PostData.Add('Signature=I6euLIiVDzjZ8bbdtF840K0TJCkGh4NrUbQPtQtu78A='); // <-- NOT percent encoded yet!
IdHTTP1.Request.CustomHeaders.Values['x-amazon-user-agent'] := 'MyAppNameAndVer';
IdHTTP1.Post('http://mws.amazonservices.ca', PostData);
finally
PostData.Free;
end;
end;