CoolProfits
New Member
This may be a long shot. Hoping someone has seen this before.I'm using TweetSharp in an ASP.NET MVC 3 application to authenticate using Twitter. I have three environments: localhost, test, and production. I just moved my test server from Azure to AppHarbor (which may be irrelevant). Twitter OAuth has just broken on the test server. I'm now getting redirected back to my URL with a strange port number added to the URL:\[code\]http://test.thelocalsip.com:16472/User/TwitterCallback?oauth_token=blah&oauth_verifier=blah\[/code\]If I just remove the 16472 port, the callback works fine, and I'm logged in normally.Any ideas?Edit: seems the port is actually stuck in the callback URL I'm generating. Bad question, sorry. Voted to close it.Edit: AppHarbor is the culprit. Seems they use port numbers internally for load balancing, so when I use Url.Action to generate an absolute URL, I get the port number added.http://support.appharbor.com/kb/get...-generating-absolute-urls-without-port-number