Changeset 1122


Ignore:
Timestamp:
Feb 17, 2011, 5:21:25 AM (8 years ago)
Author:
julian.reschke@…
Message:

s/Content-Location/Content?-Disposition/

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

    r1121 r1122  
    545545      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="conformance.and.error.handling" href="#conformance.and.error.handling">Conformance and Error Handling</a></h1>
    546546      <p id="rfc.section.3.p.1">This specification defines conformance criteria for both senders (usually, HTTP origin servers) and recipients (usually, HTTP
    547          user agents) of the Content-Location header field. An implementation is considered conformant if it complies with all of the
    548          requirements associated with its role.
     547         user agents) of the Content-Disposition header field. An implementation is considered conformant if it complies with all of
     548         the requirements associated with its role.
    549549      </p>
    550550      <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,
    551551         but it does not define special handling of these invalid field-values.
    552552      </p>
    553       <p id="rfc.section.3.p.3">Sending implementations <em class="bcp14">MUST NOT</em> generate Content-Location header fields that are invalid.
     553      <p id="rfc.section.3.p.3">Sending implementations <em class="bcp14">MUST NOT</em> generate Content-Disposition header fields that are invalid.
    554554      </p>
    555555      <p id="rfc.section.3.p.4">Consuming implementations <em class="bcp14">MAY</em> take steps to recover a usable field-value from an invalid header field, but <em class="bcp14">SHOULD NOT</em> reject the message outright, unless this is explicitly desirable behaviour (e.g., the implementation is a validator). As such,
     
    967967      </ul>
    968968      <h2 id="rfc.section.D.10"><a href="#rfc.section.D.10">D.10</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-content-disp-05</a></h2>
    969       <p id="rfc.section.D.10.p.1">None yet.</p>
     969      <p id="rfc.section.D.10.p.1">Fixed two typos where the new Conformance section said "Content-Location" instead of "Content-Disposition".</p>
    970970      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    971971      <p class="noprint"><a href="#rfc.index.C">C</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.R">R</a>
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

    r1121 r1122  
    122122  This specification defines conformance criteria for both senders (usually,
    123123  HTTP origin servers) and recipients (usually, HTTP user agents) of the
    124   Content-Location header field. An implementation is considered conformant if
     124  Content-Disposition header field. An implementation is considered conformant if
    125125  it complies with all of the requirements associated with its role.
    126126</t>
     
    131131</t>
    132132<t>
    133   Sending implementations &MUST-NOT; generate Content-Location header fields
     133  Sending implementations &MUST-NOT; generate Content-Disposition header fields
    134134  that are invalid.
    135135</t>
     
    970970<section title="Since draft-ietf-httpbis-content-disp-05" anchor="changes.since.05">
    971971<t>
    972   None yet.
     972  Fixed two typos where the new Conformance section said "Content-Location" instead
     973  of "Content-Disposition".
    973974</t>
    974975</section>
Note: See TracChangeset for help on using the changeset viewer.