[Jansar]

I recently spent hours on end configuring my web server and after installing 10.2.4, IT DOESN'T WORK! Has anyone got around this one? Something must be completely changed with this update.

Don't tell me to edit my httpd.conf file again, already did that.

[timster]

Go edit your httpd.conf file again. You missed something. I tweaked mine (check for .applesaved in the directory) and it works now.

[Jansar]

Originally posted by timster:
Go edit your httpd.conf file again. You missed something. I tweaked mine (check for .applesaved in the directory) and it works now.

I see the .applesaved one. How do I use it? I edited my httpd.conf again in the following three spots as usual:

Deleted # from LoadModule php4_module libexec/httpd/libphp4.so

Deleted # from the mod_php4.c line

Added AddType application/x-httpd-php .php

[Jansar]

Nevermind, got it.

I just saved that file as httpd.conf.

[Mac Write]

I posted this in another thread (Further down) about this with a link to an article I wrote on how to get php working again, there is some extra things not mentioned here (like setting up index.php etc). It will help you restore PHP.

worked for me.

[DaveGee]

I really wish Apple would stop overwriting custom config files (like http.conf)... I've learned to live with it by making a copy (called http.conf.MINE) so now it's just second nature to just put back my config but sheech it gets annoying.

That being said, I can kinda see reasons why they do it but it doesn't make it any less annoying.

Dave

[timster]

previous system updates didnt overwrite the httpd.conf (AFAIK) - so 10.2.4 probably introduced changes to the httpd.conf that might not have been compatible with older versions.

I did a 'diff' on the older .conf and the newer one and it seems like the only things Apple added was the rendezvous module and the rendezvous configuration directive. hard to imagine that'd really require a stock configuration file, but I guess they were just playing it safe for those who might have already configured mod_rendezvous. *shrug*

[Rainy Day]

Originally posted by DaveGee:
I really wish Apple would stop overwriting custom config files (like http.conf)... I've learned to live with it by making a copy (called http.conf.MINE) so now it's just second nature to just put back my config but sheech it gets annoying.

Notice the last line of Apple's http.conf file:

Include /private/etc/httpd/users

That's intended to load http.conf customizations for individual users on your Mac. What it does, effectively, is append every file in the directory /private/etc/httpd/users/, in alphabetical order, to your /etc/httpd/httpd.conf file. So if you place a file containing only the customizations you would otherwise make to /etc/httpd/httpd.conf in the directory /private/etc/httpd/users/, your customizations will always be in effect without ever editing your /etc/httpd/httpd.conf file. Slick, eh?

Important safety tip: Every file in /private/etc/httpd/users/ is appended to your /etc/httpd/httpd.conf file, even files with suffixes like ".bak", so keep your backup files in another directory, else they are likely to override the changes you're making in your primary file (e.g. my.httpd.conf.bak would load after my.httpd.conf, which might undo the edits you've made and send you off chasing your tail for hours while trying to figure out why the changes you're making don't seem to work properly -- of course i was never caught by this snare! ).

[Terri]

Originally posted by Rainy Day:
Notice the last line of Apple's http.conf file:

Include /private/etc/httpd/users

That's intended to load http.conf customizations for individual users on your Mac. What it does, effectively, is append every file in the directory /private/etc/httpd/users/, in alphabetical order, to your /etc/httpd/httpd.conf file. So if you place a file containing only the customizations you would otherwise make to /etc/httpd/httpd.conf in the directory /private/etc/httpd/users/, your customizations will always be in effect without ever editing your /etc/httpd/httpd.conf file. Slick, eh?

Important safety tip: Every file in /private/etc/httpd/users/ is appended to your /etc/httpd/httpd.conf file, even files with suffixes like ".bak", so keep your backup files in another directory, else they are likely to override the changes you're making in your primary file (e.g. my.httpd.conf.bak would load after my.httpd.conf, which might undo the edits you've made and send you off chasing your tail for hours while trying to figure out why the changes you're making don't seem to work properly -- of course i was never caught by this snare! ).

That is very sweet, but why doesn't Apple tell us about these things?

I already had a file in mine with my user name.conf, strange I didn't make it. The only thing in the file was this,
<Directory "/Users/create/Sites/">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

[Alex Duffield]

I just took this opertunity to update my install of PHP...

the php supplied by Mark at http://www.entropy.ch is a great build.

Also I keep all my additions to http.conf in separate files by including "Include /private/etc/httpd/v-hosts" at the end of http.conf

Then any files that are in my v-hosts folder are read in when apache starts.

That way my virtual hosts are safe from updates.

[Rainy Day]

Originally posted by Alex Duffield:
Also I keep all my additions to http.conf in separate files by including "Include /private/etc/httpd/v-hosts" at the end of http.conf

Then any files that are in my v-hosts folder are read in when apache starts.

That way my virtual hosts are safe from updates.

Just keep your v-hosts file in /private/etc/httpd/users/, then you can omit including "Include /private/etc/httpd/v-hosts" at the end of /etc/httpd/httpd.conf.