Closed GoogleCodeExporter closed 9 years ago
This will show you detailed error descriptions instead of simple not found
message.
Original comment by tmkkmac
on 7 Oct 2012 at 4:37
It says: "Netwrk connection error"
I do not have the firewall enabled. My OS is 10.7.5.
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 5:13
What country are you choosing?
Original comment by tmkkmac
on 7 Oct 2012 at 5:35
United States. I am in the US as well.
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 2:33
[deleted comment]
Then can you connect to http://ecs.amazonaws.com/onca/xml with Safari?
Original comment by tmkkmac
on 7 Oct 2012 at 3:06
Firefox:
This XML file does not appear to have any style information associated with it.
The document tree is shown below.
<Errors>
<Error>
<Code>AWS.MissingServiceParameter</Code>
<Message>Your request is missing the Service parameter. Please add the Service parameter to your request and retry.</Message>
</Error>
</Errors>
Safari:
AWS.MissingServiceParameterYour request is missing the Service parameter.
Please add the Service parameter to your request and retry.
Chrome:
This XML file does not appear to have any style information associated with it.
The document tree is shown below.
<Errors>
<Error>
<Code>AWS.MissingServiceParameter</Code>
<Message>Your request is missing the Service parameter. Please add the Service parameter to your request and retry.</Message>
</Error>
</Errors>
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 5:43
Well, how about Safari? XLD uses CFNetwork backend for connection, so the
result with Safari is important.
Original comment by tmkkmac
on 7 Oct 2012 at 5:49
Repeating the Safari result:
Safari:
AWS.MissingServiceParameterYour request is missing the Service parameter.
Please add the Service parameter to your request and retry.
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 6:08
OK. Then please post messages from XLD when using this version. The messages
appear in Console.app.
http://tmkk.pv.land.to/xld/XLD_dev_121008.zip
Original comment by tmkkmac
on 7 Oct 2012 at 6:23
From Console:
10/7/12 2:28:48.765 PM XLD: Connecting to
http://ecs.amazonaws.com/onca/xml?AWSAccessKeyId=YOUR_AWS_KEY&AssociateTag=tmkk-
22&Keywords=alien&Operation=ItemSearch&ResponseGroup=Small%2CImages&SearchIndex=
All&Service=AWSECommerceService&Timestamp=2012-10-07T18%3A28%3A48Z&Signature=uwc
497tNevvHcnpaX9gqJXo21009Rj5nE2UVtDA5/6U%3D
10/7/12 2:28:48.768 PM XLD: bad URL
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 6:29
[deleted comment]
Oh, and the error has changed in then new debug XLD. It now says:
Network eonnection error: bad URL
The AWSAccessKeyId portion of the URL seems to have a placeholder:
YOUR_AWS_KEY
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 6:35
I guess your AWS key includes whitespace or something like. Please check it.
Original comment by tmkkmac
on 7 Oct 2012 at 6:47
I have edited the access key/secret key a few times. There was a leading space
in the access key.
I re-entered both keys and now the connection error is gone.
That said, the original issue of not being able to match any results remains. I
searched for Foo Fighters, no results returned. Foo, no results. Rolling
Stones, no results.
The latest debug binary says "Not Found" each time and the console log shows:
10/7/12 2:54:05.778 PM XLD: Connecting to
http://ecs.amazonaws.com/onca/xml?AWSAccessKeyId=YOUR_AWS_KEY&AssociateTag=tmkk-
22&Keywords=Foo%20Fighters&Operation=ItemSearch&ResponseGroup=Small%2CImages&Sea
rchIndex=All&Service=AWSECommerceService&Timestamp=2012-10-07T18%3A54%3A05Z&Sign
ature=jD6N5DdBOAwErSaWdmRLMBDVNTYFNoahkmvFTbdX9xo%3D
So the connection error was due to a leading space in the Access Key. Maybe the
lack or results returned is an AWS issue?
Thanks for all your help.
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 6:59
At least when I search for Foo Fighters in US AWS server it works properly.
Please send me the messages when using this version:
http://tmkk.pv.land.to/xld/XLD_dev_121008-2.zip
This time the messages include your AWS key, so do not post here for security.
Send a mail to tmkkmac at gmail dot com.
Original comment by tmkkmac
on 7 Oct 2012 at 7:11
I have posted the console log via email.
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 7:19
Relevent error when I post this into a browser:
<Errors>
<Error>
<Code>AWS.InvalidAccount</Code>
<Message>Your AccessKey Id is not registered for Product Advertising API. Please use the AccessKey Id obtained after registering at https://affiliate-program.amazon.com/gp/flex/advertising/api/sign-in.html.</Message>
</Error>
</Errors>
It seems my AWS account may not be properly configured?
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 7:22
I went to the URL posted above and added the Product Advertising API. It now
works. Maybe a handler can be added for this error?
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 7:27
Thank you for all your help on this one. I had never changed my AWS settings
since creating it years ago. I think things changed on their end.
Once I specifically added the Product Advertising API to my account, things are
back to the way they used to be.
Thank you, again, for all your help here.
Original comment by halfsqua...@gmail.com
on 7 Oct 2012 at 7:30
closing
Original comment by tmkkmac
on 7 Oct 2012 at 7:32
Issue 160 has been merged into this issue.
Original comment by tmkkmac
on 19 Feb 2013 at 4:06
Issue 185 has been merged into this issue.
Original comment by tmkkmac
on 25 Jun 2013 at 5:20
Issue 185 has been merged into this issue.
Original comment by tmkkmac
on 28 Jan 2015 at 8:46
Original issue reported on code.google.com by
halfsqua...@gmail.com
on 7 Oct 2012 at 12:30