Page 1 of 1
HUGE Problem! Site won't work on Internet Explorer!
Posted: Fri Jun 08, 2007 7:44 pm
by MrAirsoft
My site
http://www.mrairsoft.com will not work on Internet Explorer. We've been fine until we installed SSL. We had initial problems with Firefox but then we fixed those completely, and then we checked Internet Explorer and it was COMPLETELY messed up! So we figured that the SSL was the problem, and we removed SSL, and the site was STILL messed up on Internet Explorer! So right now SSL is back to secure Firefox users, but things on Internet Explorer... they're completely messed up. Please email
matt@mrairsoft.com (I'm actually Justin, his partner) with any solutions you may have, or respond to this thread.
Posted: Fri Jun 08, 2007 7:57 pm
by nickvd
Your problem stems from referencing both secure (https://) and non-secure (http://) items...
Change them all to secure items (links, images, stylesheets, javascript, etc) and the problem will likely go away...
Posted: Fri Jun 08, 2007 11:23 pm
by Benjamin
This is a client side issue.
Posted: Fri Jun 08, 2007 11:32 pm
by AKA Panama Jack
No, it's a server side issue.
You have a mixture of both secure and non-secure links and images. This will always cause problems.
For some reason you have hardcoded the URL for most things and that is a bad thing.
Like this...
<a href="
http://mrairsoft.com/index.php?cPath=21 ... ories-></a>
It is a non-secure link but when you click on it you are going to a secure url.
https://mrairsoft.com/index.php?cPath=2 ... 300a0d8357
Your links should be setup like this...
<a href="index.php?cPath=21&osCsid=06cb7cff655dd1e011ddc8300a0d8357">Accessories-></a>
This will avoid many problems. The same thing for some of your images.
I bet you are using something like mod_rewrite to change the http:// to https:// to avoid having to change all of your hardcoded urls and that is a very, VERY bad practice.
Also, for a site like yours you should only use https:// when the client is going to the checkout. The main site should stay http:// Like I said before I bet you took a few shortcuts to make the site use https://. Shortcuts and https:// just don't work well together.
And you really need to hide osCsid=06cb7cff655dd1e011ddc8300a0d8357 in a secure cookie that expires after a few minutes.
Posted: Sat Jun 09, 2007 1:22 pm
by MrAirsoft
Yeah, that extra stuff in the URL was being a problem. Thank you guys very much, although I'm likely not done here, but thanks and I will take the tips here and put them into action.
Posted: Sat Jun 09, 2007 1:47 pm
by Benjamin
AKA Panama Jack wrote:No, it's a server side issue.
html is not a php issue. The errors are in IE, caused by html, I'm sticking with my original opinion.
Posted: Sat Jun 09, 2007 2:38 pm
by AKA Panama Jack
astions wrote:AKA Panama Jack wrote:No, it's a server side issue.
html is not a php issue. The errors are in IE, caused by html, I'm sticking with my original opinion.
Then you have never worked with HTTPS before to make that claim. It is all server side. You have to be sending the PROPER information to the client.
Both Opera and Firefox will allow what he is doing but warnings will be issued if you check the browser error consoles.
And HTML CAN be a php issue since PHP is used to generate the HTML output from the server. If the PHP code is generating improper HTML then it is a PHP issue.
I know IE is crap and full of problems but in this case it is NOT an IE issue but poorly created HTML by PHP from the server.