Callback URL for Chrome extension

anton_byrna · 2011-09-17T12:42:59.000Z

I can’t to setup callback url for chrome extension, I suppose it because protocol in url contains symbol “-” and url doesn’t have domain name. The url is look like “chrome-extension://my_ext_id_here/options.html”

anton_byrna · 2011-09-19T11:19:00.000Z

I found solution: if url will be shortened for example with tinyURL it will be working. But I think it’s not best way so I hope you’ll update validation for callback URL in settings form.

episod · 2011-09-19T14:29:42.000Z

On the settings form, you need only provide a valid URL it understands as a placeholder. When performing the OAuth sequence, you should send an explicit (non-shortened) callback URL to the request token method, using the protocol (chrome-extension) and all.

anton_byrna · 2011-09-19T14:44:46.000Z

The point is that the url failing on validate — http://cl.ly/1q132Q1i3S1R0P3k2w2I it seems that developers in twitter believe that this url is not valid.

anton_byrna · 2011-09-19T14:45:46.000Z

Answered you below.

episod · 2011-09-19T15:32:17.000Z

Correct – we don’t accept custom URI schemes on the dev.twitter.com form – for your placeholder URL it needs to be a http or https-based URL. But on the request_token step of OAuth you are permitted to use any valid URI scheme you like.

anton_byrna · 2011-09-20T07:47:20.000Z

Thanks a lot it was helped but behaviour is little strange.

episod · 2011-09-20T14:02:10.000Z

Agreed; the unintuitive logic of this has long been a pet peeve of mine. We’ll eventually abstract away the current UI so that the choice is a bit more deliberate and transparent.