Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: incrediBILL
I'm using PHP on Apache and have many sites operating on the same server without problem. It just seems to affect this one site.
I've checked that zlib output compression is off because I've heard that there is a bug in ie6 which can cause this issue if http compression is used, so obviously that isn't it.
I've also experimented with adding various headers like..
header('Cache-Control:private') and header('Cache-Control:no-cache') in case there was some sort of caching problem going on.
The site uses global variables throughout and I've tried register globals both on and off.
What's wierd is that it just affects this one site and I can't work out why it's different to any other site I've designed which runs on this server.
It definitely only affects happens with internet explorer and I've tried it on a friends computer with ie6 and the same problem occurs.
Any theories anyone?
Actually, I've just noticed that my PHP script was outputting a line break before the <!DOCTYPE on every page of the site. I've removed it and so far it hasn't happened again, so I'm hoping that's the answer.
Does that sound a likely cause?
First - have you ever, ever experienced this in any other browser? Sometimes it will blank-page in IE, but show an error of some sort in FF.
If you can repeat the issue, it may be simpler to take the blanking-script and begin cutting out portions of it until you eliminate the bad chunk. I've had scripts die that were just fine in themselves, but were using server resources that for whatever reason were choking. Mail is a good example, on a windows server (let's not go there . . . )
[edited by: tedster at 4:55 pm (utc) on May 21, 2007]
instead of a blank page it displayed header information and source code.
Think on this one. So you're saying it failed to execute and displayed the source of your PHP to the window, is this correct?
This could be as simple as some error in your code causing the entire script to output on a print command, or something malfunctioning in the php machine on the server. Unless you can duplicate it reliably, yeah it could take days, but your other option is to ignore it and do nothing. :-)