HTTPS

[stevedurr]

Hi

When using the twitterjs script on a secured page the tweets don't load due to blocked insecure content. Looks to be the call to http://remy.github.com/twitterlib/twitterlib.js in the file.

Is here a way to fix this?

Cheers

Steve

[remy]

I'd suggest using the twitterlib script directly. It's easy to use, and
well documented (compared to my twitter.js). Also, once it's hosted on
your server (twitterlib.js that is), it's aware of https serving, and
places the API requests on the same protocol.

On 13 March 2013 20:57, stevedurr [email protected] wrote:

Hi

When using the twitterjs script on a secured page the tweets don't load
due to blocked insecure content. Looks to be the call to
http://remy.github.com/twitterlib/twitterlib.js in the file.

Is here a way to fix this?

Cheers

Steve

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7
.

[stevedurr]

Cheers for the reply Remy

I have got it working by hosting both files locally but will look at the docs for the twitterlib.

Thanks again

Steve

[bt-eric]

The protocol variable works great and knows when to use http or https. However, the twitter profile pic is served over http regardless of the protocol value. #20 fixes that by using profile_image_url_https instead of profile_image_url.