Announcement

Collapse
No announcement yet.

SSL CGI-BIN problem in Chrome

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    SSL CGI-BIN problem in Chrome

    Hi

    I have installed an SSL cert for my domain and every thing seems to be working as expected apart from when viewing cgi-bin pages in Chrome. For these pages; contact us, cart, login, checkout... Chrome says "Your connection to this site is not fully secure" Looking at the Security tab in Chrome's Developer tools the problem is mixed content. I have searched the source code for the page and can only fined https:// links

    Everything seems okay in IE.

    I would be very grateful for any help tracking down the insecure content.

    Thank you
    Lee

    #2
    The only thing I can see is the DOCTYPE statement on line 1 - it refers to
    http://www.w3.org/TR/html4/loose.dtd


    Try changing it to https://....


    Chrome picks it up. Firefox doesn't.
    Elysium:Online - Official Accredited SellerDeck Partner
    SellerDeck Design, Build, Hosting & Promotion
    Based in rural Northants

    Comment


      #3
      Hi Goz, thanks for your help. I have changed to https://www.w3.org... still getting the same message in Chrome. Looking a little deeper in to Chrome's Developer tools, it says it is something to do with index.html and favicon.ico, both of which are called over https as far as I can see.

      Comment


        #4
        I have a workaround...

        Chrome's Developer tools was saying that the favicon was the problem so, I have removed the line of code in the outer layouts that calls the favicon and now there is no mixed content message in Chrome. The path to the favicon.ico file was hard coded with https, so I can't see why removing it should make any difference.

        I have also put the http://www.w3.org/... line back to it's original form, as changing to "https" effected page formatting.

        I would like to be able to add the favico code back in

        Code:
        <link rel="shortcut icon" href="https://www.domain.net/path/favicon.ico" type="image/x-icon" />
        So, if anyone can see why would create a problem...

        Thanks
        Lee

        Comment


          #5
          Originally posted by LHorton View Post
          I have a workaround...

          Chrome's Developer tools was saying that the favicon was the problem so, I have removed the line of code in the outer layouts that calls the favicon and now there is no mixed content message in Chrome. The path to the favicon.ico file was hard coded with https, so I can't see why removing it should make any difference.

          I have also put the http://www.w3.org/... line back to it's original form, as changing to "https" effected page formatting.

          I would like to be able to add the favico code back in

          Code:
          <link rel="shortcut icon" href="https://www.domain.net/path/favicon.ico" type="image/x-icon" />
          So, if anyone can see why would create a problem...

          Thanks
          Lee

          Any reason you're quoting an exact domain path?

          If you change your code to the below, it may resolve your issue.

          Code:
          <link rel="shortcut icon" href="/path/favicon.ico" type="image/x-icon" />
          Matt. M - SMR Enterprises Ltd.

          Comment

          Working...
          X