Apache not running PHP FYI.

Interesting issue.
I installed from DVD with Apache and PHP saying both OK.
When opening PHP Page got nothing, blank screen.
When viewed source, blank, nothing again.

PHP won't even pretend it doesn't understand and send the code to the WEB
page.

Turned out that if a default page (index.php etc...) has an error PHP
bugs out for all pages, other PHP diagnosis and status pages become blank
too.

After serious contemplation, on or about Tuesday 17 October 2006 11:46
pm shaw_way@tpg.com.au perhaps from shaw_way@tpg.com.au wrote:

> Interesting issue.
> I installed from DVD with Apache and PHP saying both OK.
> When opening PHP Page got nothing, blank screen.
> When viewed source, blank, nothing again.
>
> PHP won't even pretend it doesn't understand and send the code to the
> WEB page.
>
> Turned out that if a default page (index.php etc...) has an error PHP
> bugs out for all pages, other PHP diagnosis and status pages become
> blank too.

Are you putting your files under a folder in /srv/www/htdocs? That is
where Apache and PHP look for the files. Or you can do a symlink to
the /home/yourusername/public_html folder and put them there.

--
Later,
Darrell Stec darstec@neo.rr.com

Webpage Sorcery
http://webpagesorcery.com
We Put the Magic in Your Webpages

Yes I am. This is just something I have noticed. If my code is error free
it works fine.

In most other systems if you misplace a comma or colon it sends code to
the client, which appears as text.

In my Suse 10.1 I get a blank screen with no source. Fix the code and it
is back. The funny thing is if I have an error in my default page, no PHP
page I have, incliding the phpinfo() work. It is as if PHP has stopped.

I put this up because I have seen people in other chats with similar
issues on Suse 10.1 and they have not been able to fix them.

I just came here to ask a few questions about the Apache config and PHP ini
defaults (Never saw anything like they way the default Apache config is
compartmentalized), and seeing this made me realize that we have a LOT of
work ahead of us.

It sounds to me like the PHP error messages are disabled by default. It is
indeed generally a good practice to create your own custom PHP error
messages for security reasons, but I would think the SuSe defaults would
use the PHP defaults.

Granted, I am not yet familiar with the Apache 2 config and PHP 5 default
settings, and they may indeed have them disabled by default. I would
recommend (what I'm going to do) going to the source at php.net and/or
phpfreaks.com

Dave

Okay. I think I found the answer.

In the php.net manual, there is a security section dedicated to error
messages. This explains how security is impacted by allowing error messages
and gives suggestions to avoid them (including disabling all messages)
http://us2.php.net/manual/en/security.errors.php

This should answer your question.