Re: [PHP] Re: PHP 5.2.1: Some scripts are being parsed, but most aren't

2007-03-28 Thread Mario Guenterberg
On Wed, Mar 28, 2007 at 01:50:39PM +0100, Colin Guthrie wrote:

 Should get you some output... check the headers, check the content etc.

I've checked twice the big apache log files and found some
segmentation faults! Mhm, with a vanilla apache 2.2.4 the problem
did not emerge. I would change the default apache 2.0.55 from ubuntu
to vanilla apache 2.2.4.

Greetings and thanks
Mario

-- 
 -
| havelsoft.com - Ihr Service Partner für Open Source |
| Tel:  033876-21 966 |
| Notruf: 0173-277 33 60  |
| http://www.havelsoft.com|
| |
| Inhaber: Mario Günterberg   |
| Mützlitzer Strasse 19   |
| 14715 Märkisch Luch |
 -


signature.asc
Description: Digital signature


[PHP] Re: PHP 5.2.1: Some scripts are being parsed, but most aren't

2007-03-28 Thread Colin Guthrie
Mario Guenterberg wrote:
 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 problem is very irregularly. Sometimes the effect steps on new
 scripts, sometimes on old scripts that worked before. 

Could this be some Apache thing related to gzip compression of delivery
or something? e.g. perhaps firefox says it will accept gzip therefore
apache somehow decided to send a gziped source file (which ff will
silently ungzip). But mozilla, being older, does not advertise that it
accepts gzip and therefore apache follows a different path that leads to
the scripts being handled correctly.

The above should serve as an example as I doubt that is the real cause
but you have to think laterally to solve this one... i usually test
things by telnetting to port 80

telnet host 80
GET /myscript.php HTTP/1.1
Host: www.myservername.com
cr
cr


Should get you some output... check the headers, check the content etc.

A slightly more userfriendly approach would be to use the firebug plugin
for firefox or livehttpheaders plugin and look at what the server is
supplying to you.

Hope that helps.

Col

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php