PHP sites do not load in IE

[escellentguy]

I am using IE 6 and for some reason within the past week IE will no longer load any site that involves php. I have been searching the net and have found different things but nothing seems to really hit my problem Does anyone know what this might be? Is there some activeX file that is missing or something? I reinstalled windowsxp and internet explorer.....still unable to visit sites such as bravenet.com, for example or anything that has php in the address from a link.

Any help on this would be greatly appreciated. I prefer IE but lately I have been having to switch between IE and Netscape depending on what I want to do.

Thank you in advance.

 

[smah]

It may not really be php or IE. PHP is a server side processing language that is normally used on the web for creating dynamic web pages that would be displayed in a browser. With that said, it is very common for these dynamic web pages to be created specifically for your machine using either sessions or cookies to verify or keep track of which machine is yours. So, my guess is that you have recently installed some anonymiser, firewall or proxy system that is interfering with the creation of these sessions.

 

[escellentguy]

thank you I will check into that

 

[blanius]

it's impossible for the browser to have any impact on PHP being prcessed or not. this happens on the server and only HTML is sent to the browswer. So the issue must be on the server. It could have something to do with the server detecting the browser or something.

Bret Lanius

http://bretlanius.com

 

[smah]

IE will no longer load any site that involves php

I really don't think that every site in the world using php became broken in the past couple of weeks. They all seem to work for me.

I agree that the PHP code will be processed on the server, it just may not be getting to the browser or may not be able to process because of a lack of information from the browser. Browser detection is a valid possible cause, (in addition to sessions or cookies) but the way that I read this, the root cause must ultimately be due to something on escellentguy's client machine.