Changeset 1078

Timestamp:

04/11/10 13:52:37 (12 years ago)

Author:

julian.reschke@…

Message:

clarify this document doesn't talk about C-D in payloads (see #265)

Location:

draft-ietf-httpbis-content-disp/latest

Files:

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

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

@@ -528 +528 @@
          (MIME) variant (<a href="#RFC2183" id="rfc.xref.RFC2183.1"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>) of the header field, and also clarifies internationalization aspects.
       </p>
+      <div class="note" id="rfc.section.1.p.4"> 
+         <p> <b>Note:</b> this document does not apply to Content-Disposition header fields appearing in message payloads transmitted over HTTP, such
+            as when using the media type "multipart/form-data" (<a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>).
+         </p> 
+      </div>
       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Notational Conventions
       </h1>
@@ -719 +724 @@
       <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
       </h2>
-      <table>              
+      <table>                
          <tr>
             <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
@@ -738 +743 @@
             <td class="reference"><b id="RFC2231">[RFC2231]</b></td>
             <td class="top"><a href="mailto:ned.freed@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:moore@cs.utk.edu" title="University of Tennessee">K. Moore</a>, “<a href="http://tools.ietf.org/html/rfc2231">MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations</a>”, RFC&nbsp;2231, November&nbsp;1997.
+            </td>
+         </tr>
+         <tr>
+            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
+            <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
             </td>
          </tr>
@@ -928 +938 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/264">http://tools.ietf.org/wg/httpbis/trac/ticket/264</a>&gt;: "add explanation of language tagging"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/265">http://tools.ietf.org/wg/httpbis/trac/ticket/265</a>&gt;: "Clarify that C-D spec does not apply to multipart upload"
          </li>
       </ul>
@@ -966 +978 @@
                   </li>
                   <li><em>RFC2231</em>&nbsp;&nbsp;<a href="#RFC2231"><b>9.2</b></a>, <a href="#rfc.xref.RFC2231.1">C</a></li>
+                  <li><em>RFC2388</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2388.1">1</a>, <a href="#RFC2388"><b>9.2</b></a></li>
                   <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">1</a>, <a href="#rfc.xref.RFC2616.3">2</a>, <a href="#rfc.xref.RFC2616.4">3.1</a>, <a href="#rfc.xref.RFC2616.5">3.1</a>, <a href="#rfc.xref.RFC2616.6">3.1</a>, <a href="#rfc.xref.RFC2616.7">3.1</a>, <a href="#rfc.xref.RFC2616.8">3.1</a>, <a href="#rfc.xref.RFC2616.9">6</a>, <a href="#RFC2616"><b>9.1</b></a>, <a href="#rfc.xref.RFC2616.10">A</a>, <a href="#rfc.xref.RFC2616.11">C</a><ul>
                         <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.3">2</a>, <a href="#rfc.xref.RFC2616.8">3.1</a></li>

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

@@ -96 +96 @@
   aspects.
 </t>
+<x:note>
+  <t>
+    <x:h>Note:</x:h> this document does not apply to Content-Disposition
+    header fields appearing in message payloads transmitted over HTTP, such as
+    when using the media type "multipart/form-data" (<xref target="RFC2388"/>).
+  </t>
+</x:note>
 </section>  
 
@@ -544 +551 @@
     <seriesInfo name="RFC" value="2231"/>
   </reference>
+
+  <reference anchor="RFC2388">
+    <front>
+      <title abbrev="multipart/form-data">Returning Values from Forms: multipart/form-data</title>
+      <author initials="L." surname="Masinter" fullname="Larry Masinter">
+        <organization>Xerox Palo Alto Research Center</organization>
+        <address>
+          <email>masinter@parc.xerox.com</email>
+        </address>
+      </author>
+      <date year="1998" month="August"/>
+    </front>
+    <seriesInfo name="RFC" value="2388"/>
+  </reference>
 <!--
   <reference anchor="RFC3629">
@@ -895 +916 @@
       "add explanation of language tagging"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/265"/>:
+      "Clarify that C-D spec does not apply to multipart upload"
+    </t>
   </list>
 </t>