Re: [twitter-dev] HTTP API calls redirect to HTTPS?

[Abraham Williams]

Do you perhaps have HTTPS only enabled in your profile while you make
requests from your browser?

I found that the following request redirected in Chrome when I was logged
into twitter.com but it didn't in an incognito window.

http://api.twitter.com/1/users/show/abraham.json

Abraham
-
Abraham Williams | Hacker Advocate | abrah.am
 Just launched from Answerly :
InboxQfor Chrome
@abraham  | github.com/abraham | blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.



On Thu, Apr 21, 2011 at 16:25, DustyReagan  wrote:

> I just noticed via Charles proxy that http://api.twitter.com Rest API
> calls are redirected to httpS://api.twitter.com. Is this the correct
> and permanent behavior?
>
> If so, a lot of unnecessary redirects could be trimmed if API
> developers knew to only request the HTTPS endpoint. I noticed in the
> developer documentation, the standard HTTP url is still used.
>
> Should we be using HTTPS?
>
> --
> 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
>

-- 
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

[twitter-dev] HTTP API calls redirect to HTTPS?

[DustyReagan]

I just noticed via Charles proxy that http://api.twitter.com Rest API
calls are redirected to httpS://api.twitter.com. Is this the correct
and permanent behavior?

If so, a lot of unnecessary redirects could be trimmed if API
developers knew to only request the HTTPS endpoint. I noticed in the
developer documentation, the standard HTTP url is still used.

Should we be using HTTPS?

-- 
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