rbowen 2002/07/02 19:00:12
Modified: htdocs/manual/mod core.html.en
Log:
Submitted by: Owen Boyle et al
Attempt to remove some of the confusion about what the "canonical name"
actually is. From discussion on users@
Revision Changes Path
1.226 +20 -11 httpd-docs-1.3/htdocs/manual/mod/core.html.en
Index: core.html.en
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/core.html.en,v
retrieving revision 1.225
retrieving revision 1.226
diff -u -r1.225 -r1.226
--- core.html.en 26 Jun 2002 19:01:39 -0000 1.225
+++ core.html.en 3 Jul 2002 02:00:11 -0000 1.226
@@ -3684,20 +3684,27 @@
to the same server. With <code>UseCanonicalName on</code> (and
in all versions prior to 1.3) Apache will use the <a
href="#servername">ServerName</a> and <a href="#port">Port</a>
- directives to construct a canonical name for the server. This
+ directives to construct the canonical name for the server. This
name is used in all self-referential URLs, and for the values
of <code>SERVER_NAME</code> and <code>SERVER_PORT</code> in
CGIs.</p>
+ <p>For example, if <a href="#servername">ServerName</a> is set to
+ <code>www.example.com</code> and <a href="#port">Port</a> is set to
+ <code>9090</code>, then the <em>canonical name</em> of the server is
+ <code>www.example.com:9090</code>. In the event that
+ <code>Port</code> has its default value of <code>80</code>, the
+ <code>:80</code> is ommitted from the <em>canonical name</em>.
+
<p>With <code>UseCanonicalName off</code> Apache will form
self-referential URLs using the hostname and port supplied by
the client if any are supplied (otherwise it will use the
- canonical name). These values are the same that are used to
- implement <a href="../vhosts/name-based.html">name based
- virtual hosts</a>, and are available with the same clients. The
- CGI variables <code>SERVER_NAME</code> and
- <code>SERVER_PORT</code> will be constructed from the client
- supplied values as well.</p>
+ canonical name, as defined above). These values are the same
+ that are used to implement <a
+ href="../vhosts/name-based.html">name based virtual hosts</a>,
+ and are available with the same clients. The CGI variables
+ <code>SERVER_NAME</code> and <code>SERVER_PORT</code> will be
+ constructed from the client supplied values as well.</p>
<p>An example where this may be useful is on an intranet server
where you have users connecting to the machine using short
@@ -3707,10 +3714,12 @@
slash</em> then Apache will redirect them to
<code>http://www.domain.com/splat/</code>. If you have
authentication enabled, this will cause the user to have to
- reauthenticate twice (once for <code>www</code> and once again
- for <code>www.domain.com</code>). But if
- <code>UseCanonicalName</code> is set off, then Apache will
- redirect to <code>http://www/splat/</code>.</p>
+ authenticate twice (once for <code>www</code> and once again
+ for <code>www.domain.com</code> -- see <a
+ href="../misc/FAQ.html#prompted-twice">the FAQ on this subject for
+ more information</a>). But if <code>UseCanonicalName</code>
+ is set off, then Apache will redirect to
+ <code>http://www/splat/</code>.</p>
<p>There is a third option, <code>UseCanonicalName DNS</code>,
which is intended for use with mass IP-based virtual hosting to
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
