PHP4 + Apache

morbiddk

I know this has probably been answered numerous times, but I have been messing around with different ways to install these together and I finally have them installed together. However, still when I connect to my webserver and try to display a .php file it prompts to save the file rather than open the page. This happens with any .php page on my webserver. I have installed mod_php4.c into the httpd binary. I have also added the AddType application/x-httpd-php .php and AddType application/x-httpd-php-source .phps lines to my httpd.conf to no avail. when I do httpd -l here are the results:
$ httpd -l
Compiled-in modules:
http_core.c
mod_env.c
mod_log_config.c
mod_mime.c
mod_negotiation.c
mod_status.c
mod_info.c
mod_include.c
mod_autoindex.c
mod_dir.c
mod_cgi.c
mod_asis.c
mod_imap.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_rewrite.c
mod_access.c
mod_auth.c
mod_so.c
mod_setenvif.c
mod_php4.c

So the php4 mod is 'supposidly' installed into the binard. I also have the DSO module installed libphp4.so. And when I put LoadModule php4_module /usr/libexec/libphp4.so into my httpd.conf apache does not run at all, so currently that line is commented out. I previously had php 3.18 installed and that worked like a charm, however, one of the php scripts I have required php 4.02 or newer. Anyone have any ideas here?

Anon

Hey there-

I'm encountering all that you describe as well. Were you able to get it going?

Thanks-
k

morbiddk

Yes, I did finally get mine working. The problem that I was running into was an actual Apache problem. I am running 1.3.19 which utilized 1 conf file rather than 3, my problem was in my srm.conf, even though Apache 1.3.14 and up claim to utilize only one conf file, if the others are in the conf dir they will be read as well unless you add these 2 lines to your httpd.conf:

ResourceConfig /dev/null
AccessConfig /dev/null

After putting these in with the httpd that has the compiled mod_php4.c you don't need to load it as a module.

This cleared up my problem after debugging for a few hours. Hope this helps you out. If your using a version of Apache before 1.3.14, the fix might be something else as the folks at Apache started utilizing the single conf file in this version.