search

maheshwarirohit87 / typica

Automatically exported from code.google.com/p/typica
Apache License 2.0
0 stars 0 forks source link

Exception caught when putting value that contains * char to SimpleDB #42

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When trying to put an attribute/value that contains * character, the 
following exception is thrown:

Exception caught when trying to update the EC2Object to SimpleDB storage : 
com.xerox.amazonws.sdb.SDBException: Client error : The request signature 
we calculated does not match the signature you provided. Check your AWS 
Secret Access Key and signing method. Consult the service documentation for 
details.

Is * a special character that we should avoid? Or it's not properly URL-
encoded in Typica? I assume the client code doesn't need to URL-encode 
anything. Correct me if I am wrong.

Original issue reported on code.google.com by wen...@gmail.com on 11 Feb 2009 at 5:00

GoogleCodeExporter commented 9 years ago 
Did anyone find a solution for this?

Original comment by reid.car...@gmail.com on 23 Feb 2009 at 3:05

GoogleCodeExporter commented 9 years ago 
This is fixed in SVN and will be included in the next release. If you need an 
"unofficial" build from me, I'd be 
happy to supply one prior to a 1.5.1 release.

Original comment by dkavan...@gmail.com on 2 Mar 2009 at 8:25

GoogleCodeExporter commented 9 years ago 
I am seeing the same issue (signature we calculated...) when trying to use ids 
with
tildes in them. Specifically, "c~Fu2GswvPI". This is in version 1.5.1. Should I 
use
trunk? Is there a workaround?

Original comment by kevin...@gmail.com on 10 Apr 2009 at 6:01

GoogleCodeExporter commented 9 years ago 
Per
http://docs.amazonwebservices.com/AWSSimpleQueueService/latest/SQSDeveloperGuide
/index.html?Query_QueryAuth.html
there are four non-alphanumeric characters that should not be encoded. They are 
-_.~
the characters that are valid in URLs. I've changed SignerEncoder.java, patch is
attached. This can be applied from the top level of the project with patch -p0 <
issue-42-tilde-encoding.diff

I've tested this on my own code that is using Typica only for SimpleDB. I cannot
speak for the other services.

Original comment by kevin...@gmail.com on 10 Apr 2009 at 7:13

Attachments:

GoogleCodeExporter commented 9 years ago 
I should think 1.5.2 finally fixed this. I finally submitted and gave up my own 
encoding class which I thought 
would perform better, but seeing how it gave incorrect results, it was 
infinitely worse! I've applied the well know 
fix that uses character replacement.

Original comment by dkavan...@gmail.com on 7 Oct 2009 at 1:20