Anders
I've been working on a new build of M/DB that fixes all the issues
you've highlighted and it seems to be going well. However I have a
question regarding accented (foreign) characters. I've figured out
how to handle these in node-mdb and as far as I can see I'm
implementing it as you would *expect* SimpleDB itself to work, by
converting the accented characters to their 2-byte UTF8 representation
(eg %C3%B9 ) within the HTTP request.
However, if I try sending such a request to SimpleDB itself, I just
get the "Signatures do not match" error. I've Googled the issue and
there seems to be a recognised problem in this area. I've tried a
variety of alternatives but cannot find a way to get the request's
signature matched by SDB. However, your message implied that you've
been able to successfully save accented characters into SimpleDB, so
I'd be interested to know exactly how it's done.
For example, I can't even get Amazon's own SimpleDB scratchpad to
work, eg I get a signature mismatch error when the following is
submitted via the scratchpad:
https://sdb.amazonaws.com?DomainName=test&ItemName=item21&Attribute.1.Name=attr1&Attribute.1.Value=abc%C3%B9ef&Action=PutAttributes&Version=2009-04-15&AWSAccessKeyId=[my
key]&SignatureVersion=2&SignatureMethod=HmacSHA1&Timestamp=2011-07-06T11%3A03%3A57.000Z&Signature=[the
signature]
Note the value: abc%C3%B9ef which represents abcùef
Are you able to confirm what a valid SimpleDB request that includes
accented characters should look like in order to get correctly sign-
matched by SimpleDB?
Thanks