Hi Taylor,
Thanks for the pointers! Turned out the problem was related to
encoding. I fixed the encoding on the status in the body, and
then noticed that I wasn't encoding the '=' at the end of the
signature in the header. When I'd put the signature in the body,
it was encoded with all the other
Hi Tom/Jacky,
Thanks for replying.
I've seen a couple of places (The Hueniverse page above being one of
them) where the realm is included in the Authorization header. I
notice that this isn't the case for Twitter though so I'll remove it.
(Tried this, first time, it gave a new error 'Could not
Hi Tom/Jacky,
Thanks for responding!
Apologies if this is a double post, last one didn't seem to go
through.
I tried removing 'realm' from the Authorization header, and this
changed the
response the first time, to something like 'Couldn't authenticate you
using
OAuth', but then returned to the
Hi Everyone on this thread,
A few clarifications:
- The realm isn't required, but we'll take a realm if you provide one.
Really, it's a no-op in our system. We don't care if you have it or not, and
if you provide it, we don't do anything with it.
- Timestamp is important in that the
I am trying to get everybody who wants to test using this Mozilla REST
client, so we can have a common baseline, we can narrow source of
errors.-copy and past header here and POST
https://addons.mozilla.org/en-US/firefox/addon/9780/
Shob
On Aug 4, 9:19 am, Ben Jones
just watch the timestamps...
On Aug 4, 12:58 pm, Jacky jaga...@gmail.com wrote:
I am trying to get everybody who wants to test using this Mozilla REST
client, so we can have a common baseline, we can narrow source of
errors.-copy and past header here and POST
You are sending realm= in your Authorization header. It doesn't
belong there. ;-)
Tom
On Aug 4, 6:19 pm, Ben Jones benjamin.david.jo...@gmail.com wrote:
Hi all,
I'm currently writing my own OAuth lib for use with Twitter and have
gotten stuck whilst using the
Authorization HTTP header,
Oops, silly me, didn't read the full post. Sorry.
Make sure to watch for character encoding and timestamps. Especially
timestamps are known to cause trouble.
401 errors are almost never an issue at Twitter.
Tom
On Aug 5, 1:34 am, Tom allerleiga...@gmail.com wrote:
You are sending realm= in
