Skip to content

Fix 'Mixed Content' error by loading backend from HTTPs - #1196

Merged
jharding merged 1 commit into
twitter:gh-pagesfrom
KishanBagaria:KishanBagaria-mc-fix
Apr 27, 2015
Merged

Fix 'Mixed Content' error by loading backend from HTTPs#1196
jharding merged 1 commit into
twitter:gh-pagesfrom
KishanBagaria:KishanBagaria-mc-fix

Conversation

@KishanBagaria

Copy link
Copy Markdown
Contributor

Fixes the demo:

Mixed Content: The page at 'https://twitter.github.io/typeahead.js/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://typeahead-js-twitter-api-proxy.herokuapp.com/demo/search?q=type'. This request has been blocked; the content must be served over HTTPS.

jharding added a commit that referenced this pull request Apr 27, 2015
Load backend from HTTPs to fix Mixed Content error
@jharding
jharding merged commit fd9e76b into twitter:gh-pages Apr 27, 2015
@jharding

Copy link
Copy Markdown
Contributor

Cool, thanks!

@KishanBagaria
KishanBagaria deleted the KishanBagaria-mc-fix branch April 28, 2015 07:58
@KishanBagaria KishanBagaria changed the title Load backend from HTTPs to fix Mixed Content error Fix 'Mixed Content' error by loading backend from HTTPs Apr 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants