As I am testing my application, I am running into a weird problem with
signature generation. I am using the HMAC-SHA1 algorithm to generate a
signature key that is 40 characters long. I subsequently convert this
to bytes and base64 encode this. Comparing this with the example on I get a minor deviation, where the first signature is
generated by Twitter and the second one by me:


Subsequent tests with a reliable testing program for signature
generation gives a similar problem:


and another one:


They are so close, but still different. Does anyone have any idea what
this is ?

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to