Home/ Questions/Q 9119895
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-17T05:30:17+00:00

Love searching on Stackoverflow for answers, but this is my first post. Hopefully others

  • 0

Love searching on Stackoverflow for answers, but this is my first post. Hopefully others find this useful as well!

I have a site that needs to be https because it hosts facebook apps. I have it set up (dedicated IP and SSL certificate) but when I visited it via https I get the following warning:

This page has insecure content.

I did some research and discovered this is a common issue. Fixing our internal files is not a big deal, but we rely heavily on outside resources, like the jquery library (which is http not https). I used the Protocol Relative URL method (can’t post link because I’m limited to two hyperlinks, so see comment below) which seems to work for a lot of people. However, when I made the changes in Chrome, I still get this warning: [blocked] The page at https://www.greetfeet.com/ ran insecure content from http://code.jquery.com/mobile/1.1.0/jquery.mobile.structure-1.1.0.min.css

If I’m having this issue I can only assume that my customers will be as well. Any idea how to fix this?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Google hosts commonly used libraries (including jQuery and jQueryUI) on HTTP and HTTPS both, e.g.:

    https://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js

    (Use this whenever you can, your users might already have it in their browser cache, making your site load up faster.)

    Other things you may need to host yourself unless reliably available for the public via HTTPS.

    The protocol relative URL is only needed if your site is accessed via HTTP by some people and HTTPS by some other people: Making resource references “protocol relative” will make people request the resource using the same protocol they used to retrieve the referencing page itself. If your site is HTTPS-only, then you don’t even need to use protocol-relative URLs, you can hard-code https:// everywhere. But it does not hurt, so you can use it nevertheless.

    • 0