Those are not the correct endpoints.
You should use
https://api.twitter.com/oauth/authorize
etc
Tom
On 9/9/10 7:34 AM, James Peter wrote:
> I'm getting some very strange intermittent errors when connecting to
> the API. It's completely take down our app. It looks like connections
> are getting reset intermittently. See a transcript below - the first
> attempt it works fine, then second two the connection resets.
> Sometimes it just hangs for minutes.
>
>
> james:~# wget http://twitter.com/oauth/authorize
> --2010-09-09 05:30:30-- http://twitter.com/oauth/authorize
> Resolving twitter.com... 128.242.240.148, 128.121.146.228,
> 128.242.245.212
> Connecting to twitter.com|128.242.240.148|:80... connected.
> HTTP request sent, awaiting response... 403 Forbidden
> 2010-09-09 05:30:30 ERROR 403: Forbidden.
>
> james:~# wget http://twitter.com/oauth/authorize
> --2010-09-09 05:30:33-- http://twitter.com/oauth/authorize
> Resolving twitter.com... 168.143.171.84, 128.121.243.228,
> 168.143.162.52
> Connecting to twitter.com|168.143.171.84|:80... connected.
> HTTP request sent, awaiting response... Read error (Connection reset
> by peer) in headers.
> Retrying.
>
> --2010-09-09 05:30:35-- (try: 2) http://twitter.com/oauth/authorize
> Connecting to twitter.com|168.143.171.84|:80... connected.
> HTTP request sent, awaiting response... Read error (Connection reset
> by peer) in headers.
> Retrying.
>
>
> Anyone else getting these problems? Doesn't happen on all the
> locations I test from, so I'm not sure if our IP has been blocked or
> go some kind of access restrictions? Our IP is 173.203.207.179
>
> Pulling my hair out trying to figure this out since it's intermittent.
>
> James
>
--
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?hl=en
