You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by sl...@apache.org on 2001/12/13 22:46:05 UTC
cvs commit: httpd-2.0/docs/manual/mod core.html
slive 01/12/13 13:46:05
Modified: docs/manual upgrading.html.en
docs/manual/mod core.html
Log:
Fix links.
Revision Changes Path
1.20 +1 -1 httpd-2.0/docs/manual/upgrading.html.en
Index: upgrading.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/upgrading.html.en,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -b -u -r1.19 -r1.20
--- upgrading.html.en 2001/12/13 21:39:28 1.19
+++ upgrading.html.en 2001/12/13 21:46:05 1.20
@@ -61,7 +61,7 @@
href="mod/mod_include.html">INCLUDES</a> are implemented on top
of the core handler, and therefore reject requests with
PATH_INFO. You can use the <a
- href="core.html#acceptpathinfo">AcceptPathInfo</a> directive to
+ href="mod/core.html#acceptpathinfo">AcceptPathInfo</a> directive to
force the core handler to accept requests with PATH_INFO and
thereby restore the ability to use PATH_INFO in server-side
includes.</li>
1.206 +1 -1 httpd-2.0/docs/manual/mod/core.html
Index: core.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.html,v
retrieving revision 1.205
retrieving revision 1.206
diff -u -d -b -u -r1.205 -r1.206
--- core.html 2001/12/13 21:39:28 1.205
+++ core.html 2001/12/13 21:46:05 1.206
@@ -188,7 +188,7 @@
<dt><code>default</code><dd>The treatment of requests with
trailing pathname information is determined by the <a
- href="../handlers.html">handler</a> responsible for the request.
+ href="../handler.html">handler</a> responsible for the request.
The core handler for normal files defaults to rejecting PATH_INFO.
Handlers that serve scripts, such as <a
href="mod_cgi.html">cgi-script</a> and <a