<usage>
<p>The <directive>ServerPath</directive> directive sets the legacy
URL pathname for a host, for use with <a
- href="../vhosts/">name-based virtual hosts</a>.</p>
+ href="../vhosts/name-based.html">name-based virtual hosts</a>.</p>
+
+ <note><p>This is a legacy feature for providing compatibility with
+ HTTP/1.0 clients that do not send a <code>Host:</code> header. When
+ such a client requests a URL matching a vhost's
+ <directive>ServerPath</directive>, the request is served from that
+ vhost. In practice, all modern HTTP clients send the
+ <code>Host:</code> header, making this directive unnecessary.</p></note>
</usage>
-<seealso><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></seealso>
+<seealso><a href="../vhosts/name-based.html">Name-based Virtual Host Support</a></seealso>
+<seealso><a href="../vhosts/examples.html#serverpath">ServerPath example</a></seealso>
</directivesynopsis>
<directivesynopsis>
file with the specified IP address has the highest priority
and catches any request to an unknown server name, or a request
without a <code>Host:</code> header field (such as a HTTP/1.0
- request).</p>
+ request). If a <directive module="core">ServerPath</directive>
+ is configured for any of the matching vhosts, and the request URL
+ matches that path, the request is served from that vhost instead.
+ This is a legacy mechanism for HTTP/1.0 clients that do not send
+ a <code>Host:</code> header; see the
+ <a href="examples.html#serverpath">ServerPath example</a> for
+ details.</p>
</section>