Whether you plug your token in or not shouldn't matter -- the callback
script should fire when you call the URL, regardless. All you're
looking for is a page load here, whether it errors or not.
As I said, the problem is clearly one on your end, if you can't load
the callback page by calling it directly in a browser.
If you haven't already, check your logs. (Firewall messages, Apache or
whatever other server, etc. etc. Particularly Apache, if this all
started with .htaccess issues.)
∞ Andy Badera
∞ +1 518-641-1280 Google Voice
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me: http://www.google.com/search?q=andrew%20badera
On Sat, Nov 7, 2009 at 1:17 PM, Mike <mike_p...@hotmail.com> wrote:
> Do you mean to manually go to the page on my site that Twitter
> redirects you to after performing OAuth, and plug in the OAuth token
> into the URL?
> If so, that did nothing either. The site still hung.
> - Mike
> On Nov 7, 2:19 am, Andrew Badera <and...@badera.us> wrote:
>> What happens if you plug in your callback URL locally into a browser?
>> Same result, or does the page successfully load?
>> ∞ Andy Badera
>> ∞ +1 518-641-1280 Google Voice
>> ∞ This email is: [ ] bloggable [x] ask first [ ] private
>> ∞ Google me:http://www.google.com/search?q=andrew%20badera
>> On Fri, Nov 6, 2009 at 3:12 PM, Mike <mike_p...@hotmail.com> wrote:
>> > I have been developing a Twitter application for the past several
>> > weeks and have had no problems whatsoever interfacing with the Twitter
>> > API for authentication and updating profile settings. I am developing
>> > this app on a shared Linux hosting plan through GoDaddy, if that makes
>> > any difference.
>> > Last night, I was incorporating some URL rewriting functions into the
>> > htaccess file and suddenly whenever I went to sign in to my app via
>> > Twitter, the site would hang. What would happen exactly is I would
>> > click "sign in" on my site, get redirected to Twitter to enter my
>> > login info, and then the browser would just hang at the Twitter screen
>> > with the message "Redirecting you back to the application". A few
>> > minutes later, the browser would report the server dropped the
>> > connection, or something to that effect.
>> > I then undid all of the URL rewriting changes to the htaccess file and
>> > restored all of the pages to their original states (before the URL
>> > rewriting) but this did not have any effect. I was still seeing the
>> > same problem. I have tested this on several different browsers, all
>> > with the same results.
>> > However, I am intermittently able to connect and get successfully
>> > redirected back to my app; however, this is pretty rare. The
>> > redirection might work 1 time out of every 8 attempts.
>> > I called GoDaddy and after spending a total of almost 10 minutes on
>> > hold, the tech informed me that everything was fine with their server.
>> > I am using OAuth and Jason Mathai's Twitter-async PHP wrapper to
>> > communicate with the API, which has been working great for me.
>> > I am about to tear my hair out over this. I really have no clue where
>> > to begin troubleshooting. If anyone can help, I would truly appreciate
>> > it.
>> > Thanks.