Changeset 1189


Ignore:
Timestamp:
Mar 14, 2011, 2:33:44 PM (9 years ago)
Author:
julian.reschke@…
Message:

add fwd ref to section defining validity

Location:
draft-ietf-httpbis-content-disp/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

    r1188 r1189  
    558558         the requirements associated with its role.
    559559      </p>
    560       <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,
    561          but it does not define special handling of these invalid field-values.
     560      <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
     561         (<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.
    562562      </p>
    563563      <p id="rfc.section.3.p.3">Senders <em class="bcp14">MUST NOT</em> generate Content-Disposition header fields that are invalid.
     
    716716         <dd>IETF</dd>
    717717         <dt>Specification document:</dt>
    718          <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.1" title="Header Field Definition">Section&nbsp;4</a>)
     718         <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.2" title="Header Field Definition">Section&nbsp;4</a>)
    719719         </dd>
    720720      </dl>
     
    10301030      <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>
    10311031      <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
    1032          actual filename.
     1032         actual filename. Added a forward reference from "invalid" to the section that defines a valid header field.
    10331033      </p>
    10341034      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
     
    10381038         <ul class="ind">
    10391039            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
    1040                   <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>
     1040                  <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>
    10411041               </ul>
    10421042            </li>
     
    10441044                  <li>Header Fields&nbsp;&nbsp;
    10451045                     <ul>
    1046                         <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>
     1046                        <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>
    10471047                     </ul>
    10481048                  </li>
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

    r1188 r1189  
    127127<t>
    128128  This specification also defines certain forms of the header field-value to be
    129   invalid, using both ABNF and prose requirements, but it does not define
    130   special handling of these invalid field-values.
     129  invalid, using both ABNF and prose requirements (<xref target="header.field.definition"/>),
     130  but it does not define special handling of these invalid field-values.
    131131</t>
    132132<t>
     
    10601060  Rephrase the requirement about well-known file system locations, and also
    10611061  clarify that by "last path segment" we mean the actual filename.
     1062  Added a forward reference from "invalid" to the section that defines a valid
     1063  header field.
    10621064</t>
    10631065</section>
Note: See TracChangeset for help on using the changeset viewer.