Ok, this is what I have.

- I am using HTTP headers
- I am using POST.
- Regarding SSL, does that mean I have to use https instead of http?
If that's so, then I am doing it. I'm unaware if there's something

- I'm unsure of what you mean by this and the next point. This is my

- Here's my signature base string:

I am signing it with my consumer secret followed by an ampersand
(since I don't have a token for this request).

This is the URL I'm trying to access: https://api.twitter.com/oauth/access_token

And these are my header fields:
Authorization = "OAuth realm=\"\", oauth_consumer_key=\"edited\",
oauth_signature_method=\"HMAC-SHA1\", oauth_signature=
\"fXz8BNFXbesfsSSE5TKfAyNoRYg%3D\", oauth_timestamp=\"1272590525\",
oauth_nonce=\"CF34FD8C-ADF6-4A2E-BBE9-8650A8ACF96D\", oauth_version=
    "X-Twitter-Client" = "Edited";
    "X-Twitter-Client-Url" = "Edited";
    "X-Twitter-Client-Version" = "0.1";

I'm a bit lost here. I'm not new regarding HTML, but requests have
been a little too much. Any idea what I'm doing wrong?


Reply via email to