Apache / PHP segfaulting?

[Hangaku]

Sometimes while I'm browsing the forums, I'll click a link, and my browser prompts me to download a PHP file. This means that for whatever reason, Apache was unable to process the file normally (for example, something might be segfaulting).

Can anyone confirm or deny this? It happens randomly. And after I cancel the downloading of the .php file, the server then takes longer to respond to the next page load than normal.

[netoperek]

Does it happen on many different servers? Does php files actually have any php code in it or is it processed already? If the answer for both question is Yes, i want to have a copy of Your browser

[Steven]

I haven't seen any such problems here on f1technical.net so far...

[Hangaku]

Just happened again:

[Hangaku]

I've downloaded the file and taken a look at it. It's mostly binary data, so nonsensical, but the file header is as follows:

Code: Select all

HTTP/1.1 200 OK
Date: Wed, 20 Apr 2011 08:16:40 GMT
Server: Apache/1.3.34 (Debian) mod_ssl/2.8.25 OpenSSL/0.9.8c
Cache-Control: private, no-cache="set-cookie"
Content-Encoding: gzip
Expires: 0
Pragma: no-cache
Vary: Accept-Encoding
X-Powered-By: PHP/5.2.12-0.dotdeb.0
Keep-Alive: timeout=15, max=97
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

[Steven]

I see nothing wrong with the headers.
Is that opera you're using? Which version?

[Sebp]

That's the new Firefox 4

[Steven]

Ah yes indeed...
I was hoping it was opera somehow, as I haven't seen any issue with firefox4 (my daily browser). Hence I have no idea really where to start on this...

[Dragonfly]

I am running FF4 for quite a time now on 2 PC's and a laptop and haven't had any such problems.

[Hangaku]

Ah yes indeed...
Hence I have no idea really where to start on this...

Have you taken a look in /var/log/messages, at around the time when I got the problem (noted in the header). If one of the apache threads is causing a segmentation fault, it (should) have an entry.

I can tell you it's certainly not my browser causing it, as I've seen it both at home and at work, on totally different browsers / operating systems. (Windows + Firefox, Linux + Google Chrome).