[nutbits]

It was copied as httpd.conf.applesaved in /etc/httpd/
After a moment of panic, it was easy to fix, but why did they do that?
Did this happen to anyone else?

[alex_kac]

They do it almost every update. You're actually NOT supposed to edit the httpd.conf. Instead, there is a directive at the bottom of the Apple httpd.conf that calls a user.conf type thing where all your directives should go. Those directives override the apple ones.

I haven't done this myself, but read about it in past forums. Maybe a search might help.

[kvm_mkdb]

Originally posted by nutbits:
After a moment of panic, it was easy to fix, but why did they do that?
Did this happen to anyone else?

Because they added a rendezvous module for apache, which also needs its own directives.

[Wevah]

The installer backed up my old conf file to /etc/httpd/httpd.conf.applesaved .

On a similar note: does anyone know what the directives for mod_rendezvous_apple are?

[kvm_mkdb]

Originally posted by Wevah:
does anyone know what the directives for mod_rendezvous_apple are?

RegisterDefaultSite
Optionally, specify a port or keyword main; defaults to 80

RegisterUserSite username
Specify a user name or the keyword all-users, optionally followed by a port or keyword main; default is 80

RegisterResource
Specify a path and a name under which to register, optionally followed by a port or keyword main; default is 80

[Wevah]

Sweet; thanks!

[Wevah]

Just out of curiosity, where did you grab that info from?

[kvm_mkdb]

Originally posted by Wevah:
Just out of curiosity, where did you grab that info from?

Code:
strings /usr/libexec/httpd/mod_rendezvous_apple.so | tail

[Rainy Day]

Originally posted by alex_kac:
They do it almost every update. You're actually NOT supposed to edit the httpd.conf. Instead, there is a directive at the bottom of the Apple httpd.conf that calls a user.conf type thing where all your directives should go. Those directives override the apple ones.

Funny you should mention that, cause i just posted this to the MacOS X forum:

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! ).