Best practice for www.hostname.com vs. hostname.com for oAuth authentication errors?

KS

unread,

Apr 21, 2011, 12:47:27 PM4/21/11

to Twitter Anywhere Development

Our app callback URL is hostname.com and when a user visits using
WWW.hostname.com and tries to oAuth an error is generated saying the
callback URL is invalid.

What is the best practice fix for this? Mod_rewrite rule?

Thanks.

Daniel Chenery

unread,

Apr 21, 2011, 1:13:01 PM4/21/11

to Twitter Anywhere Development

I also had that problem. You can authorise addition domains here
https://dev.twitter.com/apps > Edit Details > authorize additional
domains
https://dev.twitter.com/apps/<APPID>/domains

Phil Johns

unread,

May 13, 2011, 5:51:07 AM5/13/11

to Twitter Anywhere Development

I recon this is the simplest way of avoiding the error:

http://www.scriptalicious.com/blog/2009/04/redirecting-www-to-non-www-using-htaccess/

Just a simple redirect to always use your domain without "www".

You could reverse it aswell so the domain always uses www if you
wanted to...

Hope this helps

On Apr 21, 5:47 pm, KS <kevinste...@gmail.com> wrote:

Reply all

Reply to author

Forward