https landing page SSL warning

4 replies
Hey there warriors,

my AM told me to add a ssl to my url and when I did it caused
my landing page to open very slow and shows warning error
when opening with IE
z1 - zuriy3k1's library

I'm told from host provider its because of the http url's
which the page has built in by default when using dreamweaver
z2 - zuriy3k1's library

is there a fix, what are my options?

thank in advance

Z
#https #landing #page #ssl #warning
  • Profile picture of the author PaybackTony
    This generally happens if you have some type of media (image, video, css, js file, etc) included in the page with a http: prefix.

    One quick way to fix it is, in Dreamweaver, on the top bar you should be able to see "Code View." Click that. Now, press ctrl+f, this will open the find/replace dialog. Once in that dialog, in the find box put "http:" and replace it with "https:". Keep doing it until dreamweaver doesn't find any more http's.

    Save and upload. This warning should go away.

    There may be a better way in DW. I use it every day, but only for the code view so I'm not certain if there's a shortcut in the wysiwyg editor.
    {{ DiscussionBoard.errors[5659919].message }}
    • Profile picture of the author zuriy3k
      Thanks for the reply... I did exactly what you said but when I clicked find it would only find my image url's that had https... but not these in this image.

      z22 - zuriy3k1's library

      z
      {{ DiscussionBoard.errors[5660071].message }}
      • Profile picture of the author PaybackTony
        Originally Posted by zuriy3k View Post

        Thanks for the reply... I did exactly what you said but when I clicked find it would only find my image url's that had https... but not these in this image.

        z
        You should be able to just put an "s" there manually.

        Also, does the printJavascript function possibly output anything that would spit out non https urls? The best way to do that is to view your site, and then view source. That should lead you to which parts are still spitting our "http:" instead of "https:"
        {{ DiscussionBoard.errors[5660208].message }}

Trending Topics