I've seen an issue similar to this a few times recently. It involved a phpBB board I log onto periodically. It seems that the server is really slow and after what seems to be a timeout period, sometimes I'll get a download request in Firefox. If I let it download, I get an empty file. I was worried that it was flaking and was actually sending PHP source code, but it didn't. This seems to only happen if the server times out. Like maybe the server is sending the PHP script to the PHP engine and not getting a response back as fast as it would like so it's assuming the engine failed. I've seen it happen once on another server, but this other server (again with phpBB) seems to be a bit quicker so only saw the issue once. But it appeared to be similar circumstances.. some kind of timeout interpretting the PHP script. Not sure if it's a web server issue. If maybe there's a setting in Apache to say "wait another 5 seconds for script interpretting to be done" and it wouldn't happen anymore. Don't know and don't have time to research. Just wanted to share a similar experience in case it gives any clues as to why yours is doing what it's doing. -TG = = = Original message = = = Zolt~~n N~~meth wrote: > 2007. 03. 28, szerda keltez~~ssel 14.42-kor Mario Guenterberg ezt ~~rta: > >> On Wed, Mar 28, 2007 at 07:20:37AM -0500, Myron Turner wrote: >> >>> It's hard to see how this could be a browser issue. Firefox does not >>> parse the scripts. The scripts are parsed on the server, under Apache. >>> The server outputs the result of the parsing and the browser displays >>> the result. >>> >> I know that the browser does not parse the scripts. But what the >> hell is the problem? I have changed the apache log settings to debug >> and nothing to see in the log files. The amusing of this is the >> old mozilla works fine with the same script. Firefox pop up a download >> window. The script is well formed, <?php ?> tags are included. I >> would not be surprised when I see the source of the script in >> firefox. But a download window??? >> > > the download window is maybe because of incorrect content-type headers. > it is possible that the older browser does not take care about that > header, so the content is displayed ok, but the newer browser reads the > header, cannot interpret it and so offers the download window > > check out what headers are the script is sending out > > greets > Zolt~~n N~~meth > > >> The problem is very irregularly. Sometimes the effect steps on new >> scripts, sometimes on old scripts that worked before. >> >> Greetings >> Mario >> >> > > I think you have to keep in mind that the headers would not affect the actual content being sent to the browser from the server. If the script is parsed as php on the server, it will be sent as text/html to the browser and displayed as parsed. But if the server does not parse the script then the browser will receive a copy of the script itself and depending then on whether the browser recognizes the content-type as displayable, it will either display it or ask if you want to download it. -- _____________________ Myron Turner http://www.room535.org http://www.bstatzero.org http://www.mturner.org/XML_PullParser/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php ___________________________________________________________ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
