Correct links as spooted in comment in online doc

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

diff --git a/docs/manual/compliance.html.en b/docs/manual/compliance.html.en
index 3d856151537e98ade3f67853eb543d19d1b072f0..84669f9b1a682bc9758ad3c4c065836dfac31253 100644 (file)
--- a/docs/manual/compliance.html.en
+++ b/docs/manual/compliance.html.en
@@ -182,7 +182,7 @@
     
     <p>There are a number of ways of determining the length of a response
     body, described in full in
-    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec4.4">
+    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4">
     RFC2616 section 4.4 Message Length</a>.</p>
     
     <p>When the <code>Content-Length</code> header is present, the size of
@@ -229,7 +229,7 @@
 
     <p>The media type of the body is placed in the <code>Content-Type</code>
     header, and the format of the header is described in full in
-    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec3.7">
+    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7">
     RFC2616 section 3.7 Media Types</a>.</p>
     
     <p>A syntactically valid content type might look as follows:</p>
@@ -266,7 +266,7 @@
     
     <p>There are a number of ways of determining the length of a response
     body, described in full in
-    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec4.4">
+    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4">
     RFC2616 section 4.4 Message Length</a>.</p>
     
     <p>When the <code>Content-Length</code> header is present, the size of
@@ -330,7 +330,7 @@
 
     <p>Full details of how a freshness lifetime is calculated is described in
     full in
-    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec13.2">
+    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2">
     RFC2616 section 13.2 Expiration Model</a>.</p>
 
     <p>During the freshness lifetime, a cache does not need to contact the

diff --git a/docs/manual/compliance.xml b/docs/manual/compliance.xml
index 3d8a02538368a3d2a81acbbf6421d0dabd7a749c..1449353520d476fb55c9db584f15b5f085e4e588 100644 (file)
--- a/docs/manual/compliance.xml
+++ b/docs/manual/compliance.xml
@@ -202,7 +202,7 @@
     
     <p>There are a number of ways of determining the length of a response
     body, described in full in
-    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec4.4">
+    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4">
     RFC2616 section 4.4 Message Length</a>.</p>
     
     <p>When the <code>Content-Length</code> header is present, the size of
@@ -256,7 +256,7 @@
 
     <p>The media type of the body is placed in the <code>Content-Type</code>
     header, and the format of the header is described in full in
-    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec3.7">
+    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7">
     RFC2616 section 3.7 Media Types</a>.</p>
     
     <p>A syntactically valid content type might look as follows:</p>
@@ -300,7 +300,7 @@
     
     <p>There are a number of ways of determining the length of a response
     body, described in full in
-    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec4.4">
+    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4">
     RFC2616 section 4.4 Message Length</a>.</p>
     
     <p>When the <code>Content-Length</code> header is present, the size of
@@ -371,7 +371,7 @@
 
     <p>Full details of how a freshness lifetime is calculated is described in
     full in
-    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec13.2">
+    <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2">
     RFC2616 section 13.2 Expiration Model</a>.</p>
 
     <p>During the freshness lifetime, a cache does not need to contact the