Changeset 1189 for draft-ietf-httpbis-content-disp

Timestamp:

14/03/11 21:33:44 (10 years ago)

Author:

julian.reschke@…

Message:

add fwd ref to section defining validity

Location:

draft-ietf-httpbis-content-disp/latest

Files:

• draft-ietf-httpbis-content-disp.html (modified) (5 diffs)
• draft-ietf-httpbis-content-disp.xml (modified) (2 diffs)

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

@@ -558 +558 @@
          the requirements associated with its role.
       </p>
-      <p id="rfc.section.3.p.2">This specification also defines certain forms of the header field-value to be invalid, using both ABNF and prose requirements,
-         but it does not define special handling of these invalid field-values.
+      <p id="rfc.section.3.p.2">This specification also defines certain forms of the header field-value to be invalid, using both ABNF and prose requirements
+         (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;4</a>), but it does not define special handling of these invalid field-values.
       </p>
       <p id="rfc.section.3.p.3">Senders <em class="bcp14">MUST NOT</em> generate Content-Disposition header fields that are invalid.
@@ -716 +716 @@
          <dd>IETF</dd>
          <dt>Specification document:</dt>
-         <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;4</a>)
+         <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.2" title="Header Field Definition">Section&nbsp;4</a>)
          </dd>
       </dl>
@@ -1030 +1030 @@
       <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></h2>
       <p id="rfc.section.E.12.p.1">Rephrase the requirement about well-known file system locations, and also clarify that by "last path segment" we mean the
-         actual filename.
+         actual filename. Added a forward reference from "invalid" to the section that defines a valid header field.
       </p>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
@@ -1038 +1038 @@
          <ul class="ind">
             <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
-                  <li>Content-Disposition header field&nbsp;&nbsp;<a href="#rfc.iref.c.1"><b>4</b></a>, <a href="#rfc.xref.header.field.definition.1">8.2</a></li>
+                  <li>Content-Disposition header field&nbsp;&nbsp;<a href="#rfc.xref.header.field.definition.1">3</a>, <a href="#rfc.iref.c.1"><b>4</b></a>, <a href="#rfc.xref.header.field.definition.2">8.2</a></li>
                </ul>
             </li>
@@ -1044 +1044 @@
                   <li>Header Fields&nbsp;&nbsp;
                      <ul>
-                        <li>Content-Disposition&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>4</b></a>, <a href="#rfc.xref.header.field.definition.1">8.2</a></li>
+                        <li>Content-Disposition&nbsp;&nbsp;<a href="#rfc.xref.header.field.definition.1">3</a>, <a href="#rfc.iref.h.1"><b>4</b></a>, <a href="#rfc.xref.header.field.definition.2">8.2</a></li>
                      </ul>
                   </li>

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

@@ -127 +127 @@
 <t>
   This specification also defines certain forms of the header field-value to be
-  invalid, using both ABNF and prose requirements, but it does not define
-  special handling of these invalid field-values. 
+  invalid, using both ABNF and prose requirements (<xref target="header.field.definition"/>),
+  but it does not define special handling of these invalid field-values. 
 </t>
 <t>
@@ -1060 +1060 @@
   Rephrase the requirement about well-known file system locations, and also
   clarify that by "last path segment" we mean the actual filename.
+  Added a forward reference from "invalid" to the section that defines a valid
+  header field.
 </t>
 </section>