Changeset 1189 for draft-ietf-httpbis-content-disp
- Timestamp:
- 14/03/11 21:33:44 (11 years ago)
- 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 558 558 the requirements associated with its role. 559 559 </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 4</a>), but it does not define special handling of these invalid field-values. 562 562 </p> 563 563 <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> 717 717 <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 4</a>)718 <dd>this specification (<a href="#header.field.definition" id="rfc.xref.header.field.definition.2" title="Header Field Definition">Section 4</a>) 719 719 </dd> 720 720 </dl> … … 1030 1030 <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a> <a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-content-disp-07</a></h2> 1031 1031 <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. 1033 1033 </p> 1034 1034 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> … … 1038 1038 <ul class="ind"> 1039 1039 <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> 1040 <li>Content-Disposition header field <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 <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> 1041 1041 </ul> 1042 1042 </li> … … 1044 1044 <li>Header Fields 1045 1045 <ul> 1046 <li>Content-Disposition <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 <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> 1047 1047 </ul> 1048 1048 </li> -
draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml
r1188 r1189 127 127 <t> 128 128 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 define130 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. 131 131 </t> 132 132 <t> … … 1060 1060 Rephrase the requirement about well-known file system locations, and also 1061 1061 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. 1062 1064 </t> 1063 1065 </section>
Note: See TracChangeset
for help on using the changeset viewer.