HTTPS Issue with IE8
-
-
- Rowan
- Rocketeer
- Posts: 55
- Thanks: 0
-
This works fine:
http://www.ptspowertech.com
This does not: https://www.ptspowertech.com
Very strange. I keep thinking I've got the answer, and then I end up back at square one again.
-
-
-
- Andy Miller
- Preeminent Rocketeer
- Posts: 9919
- Thanks: 96
- Web Kahuna
-
It's not a great solution, but if it's only ie8, you can make it act like ie7 with this in the <head> tag:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
-
-
-
- Rowan
- Rocketeer
- Posts: 55
- Thanks: 0
-
Yeah, that does make the page load as IE7 and makes the issue go away. It is a band-aid fix though.
It's just a weird issue. When I inspect either page with httpwatch in IE8, under SSL I see a 404 to www.DOMAIN.com/://0
If I navigate to either site without ssl, the /://0 link is not there.
Also, all of the images seem to returning a 304 response and not a 200. Not sure why that is. Shouldn't they be http status 200? Is the JS adding a 304 header?
Is there any way someone can see if it effects plain-vanilla installations of rocket themes over https?
I tried https on the demo.rockettheme.com site, but it redirects you to staff log in on 443 port.
-
-
-
- Shawn F
- Sr. Rocketeer
- Posts: 105
- Thanks: 0
-
I know it's been a little while on this issue, but I'm getting the same thing. I tracked down the problem, just don't know how to fix it. It's not rokbox on it's own that's causing the issue. It's Mootools. Near as I can tell, Mootools is making a xml call to/from a unsecure url.
I found a post on the internet where someone lists the same problem but no fix is listed: www.mooforum.net/solutions12/ssl-error-i...-mootools-t2028.html
-
-
-
- dilletante
- Newbie
- Posts: 8
- Thanks: 0
- Has anyone found a solution to this yet? Our site: www.overheadsolution.com/shop/ is secure in Firefox, Google Chrome, Safari, and IE 7. Only IE8 has a problem with it. There are no insecure links and it passes every SSL cert test I can run, but IE8 still gives the warning. I even tried the: <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> that Andy Miller suggested and that does not work either. Any help would be much appreciated.
-
-
-
- Rowan
- Rocketeer
- Posts: 55
- Thanks: 0
-
I just added the header that tells IE8 to bump down to 7 and things have been working. It's been a while since I've had to look at this issue, so I may have updated mootools and/or disabled rokbox as well.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="https://www.w3.org/1999/xhtml"> <head> <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
I forget if it goes in the template index.php or the main index.php. Just make sure the rendered page has it when you view source.
-
-
-
- dilletante
- Newbie
- Posts: 8
- Thanks: 0
-
Thank you for your quick response Rowan. I tried the code you suggested, (it goes in the template's index.php file) and it is rendering on the page, but IE8 is still giving the warning. Would you take a look at it and see if you are getting the warning as well?
www.overheadsolution.com/shop/
Thank you for your help.
-
-
-
- Rowan
- Rocketeer
- Posts: 55
- Thanks: 0
-
I still get the error on your site.
See if rokbox is enabled - the front end and the backend (system and content) in plug in manager.
It's a game of isolation now; switch things off until the error goes away.
My site uses this template, but it's rather plain (I have zero time to do anything to it.)
https://www.rowanwatson.com/
-
-
-
- dilletante
- Newbie
- Posts: 8
- Thanks: 0
-
Here is something interesting. Go to
www.target.com
and add something to your cart. Begin the checkout process until you get to the https secure checkout section. target.com does not throw an error in IE8, but if you look at their source you will find over 70 insecure "http:" links. Why does Target (over 70 insecure links) not throw an error, but my site:
www.overheadsolution.com/shop
(with 0 insecure links) does?
Thank you
-
Time to create page: 0.072 seconds