use example.com for example domain name

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@657842 13f79535-47bb-0310-9956-ffa450edef68

11 files changed, 53 insertions, 53 deletions

diff --git a/docs/manual/howto/public_html.xml b/docs/manual/howto/public_html.xml
index ba76f979d5..6665d61b69 100644
--- a/docs/manual/howto/public_html.xml
+++ b/docs/manual/howto/public_html.xml
@@ -123,12 +123,12 @@
       used to redirect user directory requests to external URLs.</p>
       
     <example>
-      UserDir http://www.foo.com/users/*/
+      UserDir http://example.org/users/*/
     </example>
     
     <p>The above example will redirect a request for
     <code>http://example.com/~bob/abc.html</code> to
-    <code>http://www.foo.com/users/bob/abc.html</code>.</p>
+    <code>http://example.org/users/bob/abc.html</code>.</p>
   </section>
 
   <section id="enable">
diff --git a/docs/manual/misc/security_tips.xml b/docs/manual/misc/security_tips.xml
index b51245473f..c77408587c 100644
--- a/docs/manual/misc/security_tips.xml
+++ b/docs/manual/misc/security_tips.xml
@@ -397,7 +397,7 @@
     the second example will list the ten last denied clients, for example:</p>
     
     <example>
-      [Thu Jul 11 17:18:39 2002] [error] [client foo.bar.com] client denied 
+      [Thu Jul 11 17:18:39 2002] [error] [client foo.example.com] client denied 
       by server configuration: /usr/local/apache/htdocs/.htpasswd
     </example>
     
@@ -406,7 +406,7 @@
     would have seen something similar to:</p>
     
     <example>
-      foo.bar.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1"
+      foo.example.com - - [12/Jul/2002:01:59:13 +0200] "GET /.htpasswd HTTP/1.1"
     </example>
     
     <p>in your <a href="../logs.html#accesslog">Access Log</a>. This means 
diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index c159642303..094ae78bd0 100644
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -1947,7 +1947,7 @@ URLs</description>
     functionality is especially useful when combined with the
     <directive module="core">SetHandler</directive>
     directive. For example, to enable status requests, but allow them
-    only from browsers at <code>foo.com</code>, you might use:</p>
+    only from browsers at <code>example.com</code>, you might use:</p>
 
     <example>
       &lt;Location /status&gt;<br />
@@ -1955,7 +1955,7 @@ URLs</description>
         SetHandler server-status<br />
         Order Deny,Allow<br />
         Deny from all<br />
-        Allow from .foo.com<br />
+        Allow from .example.com<br />
       </indent>
       &lt;/Location&gt;
     </example>
@@ -3152,11 +3152,11 @@ hostname or IP address</description>
     <example><title>Example</title>
       &lt;VirtualHost 10.1.2.3&gt;<br />
       <indent>
-        ServerAdmin webmaster@host.foo.com<br />
-        DocumentRoot /www/docs/host.foo.com<br />
-        ServerName host.foo.com<br />
-        ErrorLog logs/host.foo.com-error_log<br />
-        TransferLog logs/host.foo.com-access_log<br />
+        ServerAdmin webmaster@host.example.com<br />
+        DocumentRoot /www/docs/host.example.com<br />
+        ServerName host.example.com<br />
+        ErrorLog logs/host.example.com-error_log<br />
+        TransferLog logs/host.example.com-access_log<br />
       </indent>
       &lt;/VirtualHost&gt;
     </example>
diff --git a/docs/manual/mod/mod_authnz_ldap.xml b/docs/manual/mod/mod_authnz_ldap.xml
index dc0bbbba98..3daa940330 100644
--- a/docs/manual/mod/mod_authnz_ldap.xml
+++ b/docs/manual/mod/mod_authnz_ldap.xml
@@ -654,12 +654,12 @@ Require valid-user
     a User Principle Name (UPN) can be added to a user's entry in the
     directory. This UPN usually takes the form of the user's account
     name, followed by the domain components of the particular domain,
-    for example <em>somebody@nz.somedomain.com</em>.</p>
+    for example <em>somebody@nz.example.com</em>.</p>
 
     <p>You may wish to configure the <module>mod_authnz_ldap</module>
     module to authenticate users present in any of the domains making up
     the Active Directory forest. In this way both
-    <em>somebody@nz.somedomain.com</em> and <em>someone@au.somedomain.com</em>
+    <em>somebody@nz.example.com</em> and <em>someone@au.example.com</em>
     can be authenticated using the same query at the same time.</p>
 
     <p>To make this practical, Active Directory supports the concept of
@@ -675,13 +675,13 @@ Require valid-user
     an empty search root, like so:</p>
 
 <example>
-AuthLDAPBindDN apache@somedomain.com<br />
+AuthLDAPBindDN apache@example.com<br />
 AuthLDAPBindPassword password<br />
 AuthLDAPURL ldap://10.0.0.1:3268/?userPrincipalName?sub
 </example>
 
     <p>Users will need to enter their User Principal Name as a login, in
-    the form <em>somebody@nz.somedomain.com</em>.</p>
+    the form <em>somebody@nz.example.com</em>.</p>
 
 </section>
 
diff --git a/docs/manual/mod/mod_imagemap.xml b/docs/manual/mod/mod_imagemap.xml
index 9fcba6c2b1..b65c835236 100644
--- a/docs/manual/mod/mod_imagemap.xml
+++ b/docs/manual/mod/mod_imagemap.xml
@@ -218,14 +218,14 @@
       generated:</p>
 
       <example>
-        &lt;a href="http://foo.com/"&gt;<var>Menu text</var>&lt;/a&gt;
+        &lt;a href="http://example.com/"&gt;<var>Menu text</var>&lt;/a&gt;
       </example>
 
       <p>If no quoted text is present, the name of the link will be
       used as the text:</p>
 
       <example>
-        &lt;a href="http://foo.com/"&gt;http://foo.com&lt;/a&gt;
+        &lt;a href="http://example.com/"&gt;http://example.com&lt;/a&gt;
       </example>
 
       <p>If you want to use double quotes within this text, you have to
@@ -243,11 +243,11 @@
       base referer<br />
       poly map "Could I have a menu, please?" 0,0 0,10 10,10 10,0<br />
       rect .. 0,0 77,27 "the directory of the referer"<br />
-      circle http://www.inetnebr.com/lincoln/feedback/ 195,0 305,27<br />
+      circle http://www.inetnebr.example.com/lincoln/feedback/ 195,0 305,27<br />
       rect another_file "in same directory as referer" 306,0 419,27<br />
-      point http://www.zyzzyva.com/ 100,100<br />
-      point http://www.tripod.com/ 200,200<br />
-      rect mailto:nate@tripod.com 100,150 200,0 "Bugs?"<br />
+      point http://www.zyzzyva.example.com/ 100,100<br />
+      point http://www.tripod.example.com/ 200,200<br />
+      rect mailto:nate@tripod.example.com 100,150 200,0 "Bugs?"<br />
     </example>
 
 </section>
diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index a95a23c11e..8252059658 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -1196,8 +1196,8 @@ directly</description>
     <directive module="mod_proxy">ProxyRemote</directive> proxy server(s).</p>
 
     <example><title>Example</title>
-      ProxyRemote  *  http://firewall.mycompany.com:81<br />
-      NoProxy         .mycompany.com 192.168.112.0/21
+      ProxyRemote  *  http://firewall.example.com:81<br />
+      NoProxy         .example.com 192.168.112.0/21
     </example>
 
     <p>The <var>host</var> arguments to the <directive>NoProxy</directive>
@@ -1224,8 +1224,8 @@ directly</description>
     <note><title>Note</title>
       <p>Domain name comparisons are done without regard to the case, and
       <var>Domain</var>s are always assumed to be anchored in the root of the
-      DNS tree, therefore two domains <code>.MyDomain.com</code> and
-      <code>.mydomain.com.</code> (note the trailing period) are considered
+      DNS tree, therefore two domains <code>.ExAmple.com</code> and
+      <code>.example.com.</code> (note the trailing period) are considered
       equal. Since a domain comparison does not involve a DNS lookup, it is much
       more efficient than subnet comparison.</p>
     </note></dd>
@@ -1282,7 +1282,7 @@ directly</description>
     of hosts with different <var><a href="#ipaddr">IPAddr</a></var>s).</p>
 
     <example><title>Examples</title>
-      prep.ai.mit.edu<br />
+      prep.ai.example.com<br />
       www.apache.org
     </example>
 
@@ -1294,8 +1294,8 @@ directly</description>
       link.</p>
       <p><var>Hostname</var> comparisons are done without regard to the case,
       and <var>Hostname</var>s are always assumed to be anchored in the root
-      of the DNS tree, therefore two hosts <code>WWW.MyDomain.com</code>
-      and <code>www.mydomain.com.</code> (note the trailing period) are
+      of the DNS tree, therefore two hosts <code>WWW.ExAmple.com</code>
+      and <code>www.example.com.</code> (note the trailing period) are
       considered equal.</p>
      </note></dd>
     </dl>
@@ -1336,9 +1336,9 @@ directly</description>
     will be generated.</p>
 
     <example><title>Example</title>
-      ProxyRemote  *  http://firewall.mycompany.com:81<br />
-      NoProxy         .mycompany.com 192.168.112.0/21<br />
-      ProxyDomain     .mycompany.com
+      ProxyRemote  *  http://firewall.example.com:81<br />
+      NoProxy         .example.com 192.168.112.0/21<br />
+      ProxyDomain     .example.com
     </example>
 </usage>
 </directivesynopsis>
diff --git a/docs/manual/mod/mod_proxy_balancer.xml b/docs/manual/mod/mod_proxy_balancer.xml
index f3302e00d0..cec901779c 100644
--- a/docs/manual/mod/mod_proxy_balancer.xml
+++ b/docs/manual/mod/mod_proxy_balancer.xml
@@ -354,7 +354,7 @@ candidate lbstatus -= total factor</code></pre>
     <module>mod_status</module> and <module>mod_proxy_balancer</module>
     have to be present in the server.</p>
 
-    <p>To enable load balancer management for browsers from the foo.com
+    <p>To enable load balancer management for browsers from the example.com
     domain add this code to your <code>httpd.conf</code>
     configuration file</p>
 <example>
@@ -363,7 +363,7 @@ candidate lbstatus -= total factor</code></pre>
 <br />
     Order Deny,Allow<br />
     Deny from all<br />
-    Allow from .foo.com<br />
+    Allow from .example.com<br />
     &lt;/Location&gt;
 </example>
 
diff --git a/docs/manual/mod/mod_status.xml b/docs/manual/mod/mod_status.xml
index a38ac4ac25..51a4364e53 100644
--- a/docs/manual/mod/mod_status.xml
+++ b/docs/manual/mod/mod_status.xml
@@ -72,7 +72,7 @@ performance</description>
 <section id="enable">
     <title>Enabling Status Support</title>
 
-    <p>To enable status reports only for browsers from the foo.com
+    <p>To enable status reports only for browsers from the example.com
     domain add this code to your <code>httpd.conf</code>
     configuration file</p>
 <example>
@@ -81,7 +81,7 @@ performance</description>
 <br />
     Order Deny,Allow<br />
     Deny from all<br />
-    Allow from .foo.com<br />
+    Allow from .example.com<br />
     &lt;/Location&gt;
 </example>
 
diff --git a/docs/manual/mod/mod_userdir.xml b/docs/manual/mod/mod_userdir.xml
index 650a559321..71989d0e2a 100644
--- a/docs/manual/mod/mod_userdir.xml
+++ b/docs/manual/mod/mod_userdir.xml
@@ -81,7 +81,7 @@ host</context></contextlist>
     <code>Userdir</code> directive, the argument is treated as a
     filename pattern, and is used to turn the name into a directory
     specification. A request for
-    <code>http://www.foo.com/~bob/one/two.html</code> will be
+    <code>http://www.example.com/~bob/one/two.html</code> will be
     translated to:</p>
 
 <table>
@@ -97,11 +97,11 @@ host</context></contextlist>
 <table>
 <tr><th>UserDir directive used</th>
 <th>Translated path</th></tr>
-<tr><td>UserDir http://www.foo.com/users</td><td>http://www.foo.com/users/bob/one/two.html</td></tr>
+<tr><td>UserDir http://www.example.com/users</td><td>http://www.example.com/users/bob/one/two.html</td></tr>
 <tr><td>UserDir
-http://www.foo.com/*/usr</td><td>http://www.foo.com/bob/usr/one/two.html</td></tr>
+http://www.example.com/*/usr</td><td>http://www.example.com/bob/usr/one/two.html</td></tr>
 <tr><td>UserDir
-http://www.foo.com/~*/</td><td>http://www.foo.com/~bob/one/two.html</td></tr>
+http://www.example.com/~*/</td><td>http://www.example.com/~bob/one/two.html</td></tr>
 </table> 
 
 <note>
@@ -136,12 +136,12 @@ UserDir disabled user4 user5 user6
 <p>It is also possible to specify alternative user directories.
 If you use a command like:</p>
 <example>
-Userdir public_html /usr/web http://www.foo.com/
+Userdir public_html /usr/web http://www.example.com/
 </example>
-<p>With a request for http://www.foo.com/~bob/one/two.html, will try to 
+<p>With a request for http://www.example.com/~bob/one/two.html, will try to 
 find the page at ~bob/public_html/one/two.html first, then
 /usr/web/bob/one/two.html, and finally it will send a redirect
-to http://www.foo.com/bob/one/two.html.</p>
+to http://www.example.com/bob/one/two.html.</p>
 <p>If you add a redirect, it must be the last alternative in the list.
 Apache cannot determine if the redirect succeeded or not, so if you have
 the redirect earlier in the list, that will always be the alternative
diff --git a/docs/manual/mod/mod_usertrack.xml b/docs/manual/mod/mod_usertrack.xml
index 510f48f9af..bc6bfc1809 100644
--- a/docs/manual/mod/mod_usertrack.xml
+++ b/docs/manual/mod/mod_usertrack.xml
@@ -122,7 +122,7 @@ time late in the year "37".
 
     <p>The domain string <strong>must</strong> begin with a dot, and
     <strong>must</strong> include at least one embedded dot. That is,
-    <code>.foo.com</code> is legal, but <code>foo.bar.com</code> and 
+    <code>.example.com</code> is legal, but <code>foo.example.com</code> and 
     <code>.com</code> are not.</p>
 
     <note>Most browsers in use today will not allow cookies to be set
diff --git a/docs/manual/rewrite/rewrite_guide_advanced.xml b/docs/manual/rewrite/rewrite_guide_advanced.xml
index 5ec1140429..81b026deb2 100644
--- a/docs/manual/rewrite/rewrite_guide_advanced.xml
+++ b/docs/manual/rewrite/rewrite_guide_advanced.xml
@@ -587,7 +587,7 @@ RewriteRule ^/home/([^/]+)/.www/?(.*) http://<strong>www2</strong>.quux-corp.dom
 
         <dd>
           <p>Suppose we want to load balance the traffic to
-          <code>www.foo.com</code> over <code>www[0-5].foo.com</code>
+          <code>www.example.com</code> over <code>www[0-5].example.com</code>
           (a total of 6 servers). How can this be done?</p>
         </dd>
 
@@ -604,7 +604,7 @@ RewriteRule ^/home/([^/]+)/.www/?(.*) http://<strong>www2</strong>.quux-corp.dom
 
               <p>The simplest method for load-balancing is to use
               DNS round-robin.
-              Here you just configure <code>www[0-9].foo.com</code>
+              Here you just configure <code>www[0-9].example.com</code>
               as usual in your DNS with A (address) records, e.g.,</p>
 
 <example><pre>
@@ -626,15 +626,15 @@ www   IN  A       1.2.3.4
 www   IN  A       1.2.3.5
 </pre></example>
 
-              <p>Now when <code>www.foo.com</code> gets
+              <p>Now when <code>www.example.com</code> gets
               resolved, <code>BIND</code> gives out <code>www0-www5</code>
               - but in a permutated (rotated) order every time.
               This way the clients are spread over the various
               servers. But notice that this is not a perfect load
               balancing scheme, because DNS resolutions are
               cached by clients and other nameservers, so
-              once a client has resolved <code>www.foo.com</code>
-              to a particular <code>wwwN.foo.com</code>, all its
+              once a client has resolved <code>www.example.com</code>
+              to a particular <code>wwwN.example.com</code>, all its
               subsequent requests will continue to go to the same
               IP (and thus a single server), rather than being
               distributed across the other available servers. But the
@@ -661,15 +661,15 @@ www   IN  A       1.2.3.5
 
               <p>In this variant we use <module>mod_rewrite</module>
               and its proxy throughput feature. First we dedicate
-              <code>www0.foo.com</code> to be actually
-              <code>www.foo.com</code> by using a single</p>
+              <code>www0.example.com</code> to be actually
+              <code>www.example.com</code> by using a single</p>
 
 <example><pre>
-www    IN  CNAME   www0.foo.com.
+www    IN  CNAME   www0.example.com.
 </pre></example>
 
               <p>entry in the DNS. Then we convert
-              <code>www0.foo.com</code> to a proxy-only server,
+              <code>www0.example.com</code> to a proxy-only server,
               i.e., we configure this machine so all arriving URLs
               are simply passed through its internal proxy to one of
               the 5 other servers (<code>www1-www5</code>). To
@@ -709,7 +709,7 @@ while (&lt;STDIN&gt;) {
 </pre></example>
 
               <note>A last notice: Why is this useful? Seems like
-              <code>www0.foo.com</code> still is overloaded? The
+              <code>www0.example.com</code> still is overloaded? The
               answer is yes, it is overloaded, but with plain proxy
               throughput requests, only! All SSI, CGI, ePerl, etc.
               processing is handled done on the other machines.