No results

3 views
Skip to first unread message

Sam Stevens

unread,
Sep 27, 2009, 6:20:22 PM9/27/09
to SowaCS Consulting
I'm trying to generate a signed request for Amazon.

I've signed in to sowacs.appspot.com and registered my Access/Secret
Keys.

Using the sample URL provided, I plugged in my own values:
http://sowacs.appspot.com/AWS/GET/[gmaila...@domain.tld]ecs.amazonaws.com/onca/xml?ItemId=B000X9FLKM&Service=AWSECommerceService&AWSAccessKeyId=16GM21EYQRT6QQWW05G2&Operation=ItemLookup

(I replaced the Gmail account and Access Key.)

This generates an XML file without any product results.

My Access and Secret keys are fresh.

Any ideas?

C Sowa

unread,
Sep 27, 2009, 6:59:27 PM9/27/09
to SowaCS Consulting
You probably want the "Redirect" form of AWSQS usage. Just omit the
"GET/" from your request. See http://sowacs.appspot.com/AWS/Usage/Redirect.htm
for more information.

If you use "sowacs.appspot.com/AWS/GET/(request)" (or POST), AWSQS
will return an XML document that contains the signature and timestamp
for the indicated request. You would then typically retrieve those
values from the document and add them to the request yourself, and
then submit that whole thing to AWS/PAA to retrieve the desired
results. This is intended for use in somewhat more complex scenarios
than what the Redirect usage can handle.

The terminology that I've used for the different ways of using AWSQS
(Redirect vs. REST) refers to how _AWSQS_ behaves, not AWS/PAA. It's
a little confusing, since they both apply to use of the _AWS/PAA_ REST
API.
Reply all
Reply to author
Forward
0 new messages