I forgot to mention the URL I am using for the TwitterOAuth example is
not the same I used to register the application whose credentials I am
using. But I understand the URL for the app is registered just for
Twitter to know the application so this shouldn't pose any problem,
could it?

On 31 oct, 17:04, José Luis <jlgon...@ya.com> wrote:
> Hi,
>
> I'm trying TwitterOAuth's example but can't get it to authorize with
> Twitter. It gets stuck all the the time in redirect.php with the
> connection getting a 401 code all the time. I have set the consumer
> key and secret in config.php as stated in the documentation and also
> the oauth_callback. The credentials come from a registered app so they
> should be correct.
>
> I can't understand why I'm getting the 401s. Why may this be happening
> and how could I fix it?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to