sixrfan — 2012-01-02T18:50:42-05:00 — #1
chris_upjohn — 2012-01-02T19:38:51-05:00 — #2
IE has a built in fail safe that detects an SSL connection but stops any unencrypted content from entering the page without manual input from the user to override the browser, what you will need to do is ensure all <link>, <script> and <img> elements use HTTPS or you will continue to run into issues as currently your page is only partially encrypted.
ralphm — 2012-01-02T19:55:40-05:00 — #3
Another solution might be not to use the full URL in your image links. E.g. Instead of links like this:
use something like this
aussiejohn — 2012-01-02T23:25:50-05:00 — #4
Another, similar option would be to use a protocol-less URL (handy for when you do need the domain, and can't use root relative URLs)
e.g. including external scripts
<script type="text/javascipt" src="<font color='#ff0000'>//ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js</font>"></script>
e.g. including things on your own server that might be served on a different domain:
<script type="text/javascipt" src="<font color='#ff0000'>//cdn.example.com/scripts/example.js</font>"></script>
If however, everything you're referencing is on the one domain, go with Ralph.m's solution, root relative URLs
kralspace — 2012-01-19T15:25:18-05:00 — #5
I understand using the relative paths is the best way to go, but is there a way to do it if you have some pages that are several layers deep and you are using the full paths?
I also have links to other sites, does that trip the error message?
Sorry to sound so dumb, but while I can find lots of information on purchasing and installing SSL, I can find very little about the actual page coding. I have changed all the links within my website (that point to my website) to https but I still get the error message.
Anybody know of a good book? Thanks so much for your help, Kathy
aussiejohn — 2012-01-19T15:42:21-05:00 — #6
You should be able to use root-relative URLs (like in Ralph's example). They will work no matter how deep your page is nested.
The actual links themselves won't throw an error message as they aren't resources being loaded in to your page
On whichever page you're seeing that message, take a look in the source code and see if anything is being referenced with http://
kralspace — 2012-01-19T15:49:59-05:00 — #7
Thanks guys, I'll give it a try. The reason I was trying to get around using relative links with a lot of ../../../ is that I have several people who with very basic code skills are able to edit their own content and they understand the links better that way. Guess a new class is in order if they want to use the https.
I appreciate your time and expertise and will let you know how it goes Kathy
PS, I got more information here that I have all day looking through books and other websites, the Sitepoint facebook page sent me here.
aussiejohn — 2012-01-19T15:55:01-05:00 — #8
Whether you're using relative links like you're showing here or root relative links, there should be no problem as neither of them specify the protocol used (and thus they will use the protocol that is currently in use).
It might be worth teaching people about root relative links though as that can often be a much better way to go than having "../../../../../../../images/whatever.jpg"
kralspace — 2012-01-19T16:00:29-05:00 — #9
wish me luck, I work with math, science and biology teachers who are geniuses in their areas but it's a slow go getting them out of their comfort zones...lol