Comments on: Twitpic OAuth – I’m Stuck

By: toshi

toshi — Tue, 01 Jun 2010 18:33:02 +0000

thank you very much!
my mistake is OAuth libraries, that is kind of wrong.
$schema was always designated ‘http’. in function get_normalized_http_url().
changing it to Abraham’s OAuth libraries, getting things down!

By: Terence Eden

Terence Eden — Mon, 31 May 2010 17:24:02 +0000

Full details are at http://shkspr.mobi/blog/?p=2084

By: HOWTO: Twitpic and OAuth – Terence Eden has a Blog

HOWTO: Twitpic and OAuth – Terence Eden has a Blog — Mon, 31 May 2010 17:07:34 +0000

[...] am no longer confused! Here is a quick tutorial in how to post images to Twitpic and Twitter when using OAuth. I’m [...]

By: toshi

toshi — Mon, 31 May 2010 09:29:52 +0000

At last, Did you work well? if so, tell me more specific?
i got 401 “Could not authenticate you (header rejected by twitter).” now.

could you paste some code on this board?

By: Bruno Barbieri

Bruno Barbieri — Fri, 28 May 2010 23:42:37 +0000

Forget my comment. Got it workin’ too. Thank you anyway.

By: Terence Eden

Terence Eden — Wed, 26 May 2010 15:46:58 +0000

Perfect. Got it working. Thanks for all your help.

By: Stephen Corona

Stephen Corona — Mon, 24 May 2010 17:10:40 +0000

Hi Terence,

Unfortunately, with the way OAuth Echo works, we can only access the URL that you sign for (in this case, https://api.twitter.com/1/account/verify_credentials.json). This means, that we are unable to post a tweet on your behalf to twitter, because the oauth header you are signing is not for statuses/update.

Twitter is working on a solution for us, but, for the time being, you’ll have to post the tweet yourself. When you upload an image, the twitpic url is included in the JSON or XML response, so you can pull the URL from there to insert into your tweet.

By: Terence Eden

Terence Eden — Mon, 24 May 2010 16:09:02 +0000

You beauty! Nice one. Can’t believe I missed that.

All seems to work – the image appears on Twitpic, but not on Twitter. Is there a specific parameter I need to pass?

Thanks

By: Stephen Corona

Stephen Corona — Mon, 24 May 2010 13:47:24 +0000

Hi Terence,

I believe the problem is that you are signing the OAuth request using verify_credentials.xml ($fakeurl = ‘https://twitter.com/account/verify_credentials.xml). We need the request to be signed for https://api.twitter.com/1/account/verify_credentials.json. Try changing the value of $fakeurl and it should work.

By: Terence Eden

Terence Eden — Mon, 24 May 2010 11:28:22 +0000

I’ve updated the blogpost. Sending through the headers in what I think is the correct format. Now I get 401 “Could not authenticate you (header rejected by twitter).”

By: Terence Eden

Terence Eden — Mon, 24 May 2010 11:27:29 +0000

Nah, the post works. If it didn’t, Twitpic wouldn’t forward the headers on to Twitter.

By: rik

rik — Mon, 24 May 2010 09:18:28 +0000

I’d be thinking the POST thing.

By: Terence Eden

Terence Eden — Mon, 24 May 2010 09:13:02 +0000

Ah! Indeed you are wise.
The correct code should be
$header = array('X-Auth-Service-Provider: https://api.twitter.com/1/account/verify_credentials.json', 'X-Verify-Credentials-Authorization: OAuth realm="http://api.twitter.com/"');

Now at least the error I get back is from Twitter!

By: Tom Parker

Tom Parker — Sun, 23 May 2010 21:59:08 +0000

Hmm. The only immediately obvious item (yet probably unlikely as I think/hope PHP would whinge about this) is that your replacement headers have a quote inside them around the api.twitter.com bit which hasn’t been escaped like the original one was. Also, according to their example, they *all* need to have their parameters in quotes.

The error you’re getting is probably better translated to “our parser barfed, so let’s assume you didn’t give us *everything* we wanted and ergo panic”. This is an insanely annoying and common problem when trying to build this sort of thing, and unfortunately there’s a trade-off between nice error messages v.s. making it easier to find the flaws in stuff for dark-hat folks, and they tend to err on the paranoid side.

(Also, twitpic is being a bit odd with OAuth, as the spec recommends the use of HTTP POST variables for sending all this stuff…)