[PATCH] httpd-std.conf (example.com...)

[Justin Erenkrantz <je...@ebuilt.com>]

It's 5AM (rather was when I woke up).  I need to wake up.  Nothing better than
a simple search and replace to do that.  This may be overkill or entirely 
wrong, but someone else with commit access can scale back on this if they want 
or ignore it.  I don't intend to go through the source code at this point -
just the conf files seem worthy at this moment.

Essentially: 
s/.your_domain.com/.your_domain.example.com/g

I noticed that the Win32 port has @@DomainName@@ to specifically get around
this - maybe we should add something similar to the Unix install-conf target?
This may wreck havoc with "virtual servers", but uh, if they are using the
stock httpd.conf they have other problems to worry about.  

So, is there a reliable way of detecting the DNS domain name on Unix systems 
(the domainname executable is traditionally the NIS domainname).  Searching 
through resolv.conf doesn't seem like a pretty solution, but it'd work.

Hope everyone has fun at ApacheCon.  =-)  I think everyone else will be 
slightly preoccupied for the next few days... -- justin

Index: httpd-std.conf
===================================================================
RCS file: /home/cvspublic/httpd-2.0/docs/conf/httpd-std.conf,v
retrieving revision 1.28
diff -u -r1.28 httpd-std.conf
--- httpd-std.conf	2001/03/25 16:54:48	1.28
+++ httpd-std.conf	2001/04/04 13:11:53
@@ -228,7 +228,7 @@
 # e-mailed.  This address appears on some server-generated pages, such
 # as error documents.
 #
-ServerAdmin you@your.address
+ServerAdmin you@your.address.example.com
 
 #
 # ServerName allows you to set a host name which is sent back to clients for
@@ -242,7 +242,7 @@
 # You will have to access it by its address (e.g., http://123.45.67.89/)
 # anyway, and this will make redirections work in a sensible way.
 #
-#ServerName new.host.name
+#ServerName new.host.name.example.com
 
 #
 # DocumentRoot: The directory out of which you will serve your
@@ -848,25 +848,25 @@
 
 #
 # Allow server status reports, with the URL of http://servername/server-status
-# Change the ".your_domain.com" to match your domain to enable.
+# Change the ".your_domain.example.com" to match your domain to enable.
 #
 #<Location /server-status>
 #    SetHandler server-status
 #    Order deny,allow
 #    Deny from all
-#    Allow from .your_domain.com
+#    Allow from .your_domain.example.com
 #</Location>
 
 #
 # Allow remote server configuration reports, with the URL of
 #  http://servername/server-info (requires that mod_info.c be loaded).
-# Change the ".your_domain.com" to match your domain to enable.
+# Change the ".your_domain.example.com" to match your domain to enable.
 #
 #<Location /server-info>
 #    SetHandler server-info
 #    Order deny,allow
 #    Deny from all
-#    Allow from .your_domain.com
+#    Allow from .your_domain.example.com
 #</Location>
 
 #
@@ -891,7 +891,7 @@
 #<Directory proxy:*>
 #    Order deny,allow
 #    Deny from all
-#    Allow from .your_domain.com
+#    Allow from .your_domain.example.com
 #</Directory>
 
 #

Re: [PATCH] httpd-std.conf (example.com...)

["William A. Rowe, Jr." <ad...@rowe-clan.net>]

From: "Justin Erenkrantz" <je...@ebuilt.com>
Sent: Wednesday, April 04, 2001 6:30 AM


> Essentially: 
> s/.your_domain.com/.your_domain.example.com/g
> 
> I noticed that the Win32 port has @@DomainName@@ to specifically get around
> this - maybe we should add something similar to the Unix install-conf target?
> This may wreck havoc with "virtual servers", but uh, if they are using the
> stock httpd.conf they have other problems to worry about.  

Good point, sounds doable.  May I suggest we change the mechansims?

    Allow @@DomainName@@ 127.0.0.1

so that the local machine can do it's own server-status/server-info while we
are cleaning this up?

> So, is there a reliable way of detecting the DNS domain name on Unix systems 
> (the domainname executable is traditionally the NIS domainname).  Searching 
> through resolv.conf doesn't seem like a pretty solution, but it'd work.