![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 129 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 01/01/08 14:06:30 (14 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p3-payload.html (modified) (13 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r126 r129 603 603 of the charset parameter may be quoted. 604 604 </p> 605 <p id="rfc.section.2.1.p.8">Implementors should be aware of IETF character set requirements <a href="#RFC 2279" id="rfc.xref.RFC2279.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC2279]</cite></a> <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.605 <p id="rfc.section.2.1.p.8">Implementors should be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a> <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>. 606 606 </p> 607 607 <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a> <a id="missing.charset" href="#missing.charset">Missing Charset</a></h3> … … 712 712 <dl class="empty"> 713 713 <dd> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request 714 method, as described in <a href="#RFC 1867" id="rfc.xref.RFC1867.1"><cite title="Form-based File Upload in HTML">[RFC1867]</cite></a>.714 method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>. 715 715 </dd> 716 716 </dl> … … 1263 1263 <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References 1264 1264 </h2> 1265 <table summary="Informative References"> 1265 <table summary="Informative References"> 1266 <tr> 1267 <td class="reference"><b id="RFC1806">[RFC1806]</b></td> 1268 <td class="top"><a title="New Century Systems">Troost, R.</a> and <a title="QUALCOMM Incorporated">S. Dorner</a>, “<a href="http://tools.ietf.org/html/rfc1806">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</a>”, RFC 1806, June 1995. 1269 </td> 1270 </tr> 1271 <tr> 1272 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 1273 <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC 1945, May 1996. 1274 </td> 1275 </tr> 1276 <tr> 1277 <td class="reference"><b id="RFC2049">[RFC2049]</b></td> 1278 <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC 2049, November 1996. 1279 </td> 1280 </tr> 1266 1281 <tr> 1267 1282 <td class="reference"><b id="RFC2068">[RFC2068]</b></td> … … 1270 1285 </tr> 1271 1286 <tr> 1287 <td class="reference"><b id="RFC2076">[RFC2076]</b></td> 1288 <td class="top"><a title="Stockholm University/KTH">Palme, J.</a>, “<a href="http://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC 2076, February 1997. 1289 </td> 1290 </tr> 1291 <tr> 1292 <td class="reference"><b id="RFC2183">[RFC2183]</b></td> 1293 <td class="top"><a title="New Century Systems">Troost, R.</a>, <a title="QUALCOMM Incorporated">Dorner, S.</a>, and <a title="Department of Computer Science">K. Moore</a>, “<a href="http://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC 2183, August 1997. 1294 </td> 1295 </tr> 1296 <tr> 1297 <td class="reference"><b id="RFC2277">[RFC2277]</b></td> 1298 <td class="top"><a title="UNINETT">Alvestrand, H.T.</a>, “<a href="http://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP 18, RFC 2277, January 1998. 1299 </td> 1300 </tr> 1301 <tr> 1302 <td class="reference"><b id="RFC2388">[RFC2388]</b></td> 1303 <td class="top"><a 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 2388, August 1998. 1304 </td> 1305 </tr> 1306 <tr> 1307 <td class="reference"><b id="RFC2557">[RFC2557]</b></td> 1308 <td class="top"><a title="Stockholm University and KTH">Palme, F.</a>, <a title="Microsoft Corporation">Hopmann, A.</a>, <a title="Lotus Development Corporation">Shelness, N.</a>, and <a>E. Stefferud</a>, “<a href="http://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC 2557, March 1999. 1309 </td> 1310 </tr> 1311 <tr> 1272 1312 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> 1273 1313 <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999. 1314 </td> 1315 </tr> 1316 <tr> 1317 <td class="reference"><b id="RFC3629">[RFC3629]</b></td> 1318 <td class="top"><a title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, RFC 3629, STD 63, November 2003. 1319 </td> 1320 </tr> 1321 <tr> 1322 <td class="reference"><b id="RFC822">[RFC822]</b></td> 1323 <td class="top"><a title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD 11, RFC 822, August 1982. 1274 1324 </td> 1275 1325 </tr> … … 1277 1327 <h2 id="rfc.references.3"><a href="#rfc.section.9.3" id="rfc.section.9.3">9.3</a> References (to be categorized) 1278 1328 </h2> 1279 <table summary="References (to be categorized)"> 1329 <table summary="References (to be categorized)"> 1280 1330 <tr> 1281 1331 <td class="reference"><b id="RFC1766">[RFC1766]</b></td> … … 1284 1334 </tr> 1285 1335 <tr> 1286 <td class="reference"><b id="RFC1806">[RFC1806]</b></td>1287 <td class="top"><a title="New Century Systems">Troost, R.</a> and <a title="QUALCOMM Incorporated">S. Dorner</a>, “<a href="http://tools.ietf.org/html/rfc1806">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</a>”, RFC 1806, June 1995.1288 </td>1289 </tr>1290 <tr>1291 1336 <td class="reference"><b id="RFC1864">[RFC1864]</b></td> 1292 1337 <td class="top"><a title="Carnegie Mellon University">Myers, J.</a> and <a title="Dover Beach Consulting, Inc.">M. Rose</a>, “<a href="http://tools.ietf.org/html/rfc1864">The Content-MD5 Header Field</a>”, RFC 1864, October 1995. … … 1294 1339 </tr> 1295 1340 <tr> 1296 <td class="reference"><b id="RFC1867">[RFC1867]</b></td>1297 <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a> and <a title="XSoft, Xerox Corporation">E. Nebel</a>, “<a href="http://tools.ietf.org/html/rfc1867">Form-based File Upload in HTML</a>”, RFC 1867, November 1995.1298 </td>1299 </tr>1300 <tr>1301 <td class="reference"><b id="RFC1945">[RFC1945]</b></td>1302 <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC 1945, May 1996.1303 </td>1304 </tr>1305 <tr>1306 1341 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 1307 1342 <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC 2045, November 1996. … … 1314 1349 </tr> 1315 1350 <tr> 1316 <td class="reference"><b id="RFC2049">[RFC2049]</b></td>1317 <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC 2049, November 1996.1318 </td>1319 </tr>1320 <tr>1321 <td class="reference"><b id="RFC2076">[RFC2076]</b></td>1322 <td class="top"><a title="Stockholm University/KTH">Palme, J.</a>, “<a href="http://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC 2076, February 1997.1323 </td>1324 </tr>1325 <tr>1326 <td class="reference"><b id="RFC2110">[RFC2110]</b></td>1327 <td class="top"><a title="Stockholm University and KTH">Palme, J.</a> and <a title="Microsoft Corporation">A. Hopmann</a>, “<a href="http://tools.ietf.org/html/rfc2110">MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC 2110, March 1997.1328 </td>1329 </tr>1330 <tr>1331 <td class="reference"><b id="RFC2183">[RFC2183]</b></td>1332 <td class="top"><a title="New Century Systems">Troost, R.</a>, <a title="QUALCOMM Incorporated">Dorner, S.</a>, and <a title="Department of Computer Science">K. Moore</a>, “<a href="http://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC 2183, August 1997.1333 </td>1334 </tr>1335 <tr>1336 <td class="reference"><b id="RFC2277">[RFC2277]</b></td>1337 <td class="top"><a title="UNINETT">Alvestrand, H.T.</a>, “<a href="http://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP 18, RFC 2277, January 1998.1338 </td>1339 </tr>1340 <tr>1341 <td class="reference"><b id="RFC2279">[RFC2279]</b></td>1342 <td class="top"><a title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc2279">UTF-8, a transformation format of ISO 10646</a>”, RFC 2279, January 1998.1343 </td>1344 </tr>1345 <tr>1346 1351 <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 1347 1352 <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005. 1348 </td>1349 </tr>1350 <tr>1351 <td class="reference"><b id="RFC822">[RFC822]</b></td>1352 <td class="top"><a title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD 11, RFC 822, August 1982.1353 1353 </td> 1354 1354 </tr> … … 1420 1420 </p> 1421 1421 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> 1422 <p id="rfc.section.A.6.p.1">HTTP implementations which share code with MHTML <a href="#RFC2 110" id="rfc.xref.RFC2110.1"><cite title="MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2110]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not1422 <p id="rfc.section.A.6.p.1">HTTP implementations which share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not 1423 1423 fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations 1424 1424 and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section 2.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein. … … 1461 1461 </p> 1462 1462 <p id="rfc.section.C.1.p.2">Content-Base was deleted from the specification: it was not implemented widely, and there is no simple, safe way to introduce 1463 it without a robust extension mechanism. In addition, it is used in a similar, but not identical fashion in MHTML <a href="#RFC2 110" id="rfc.xref.RFC2110.2"><cite title="MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2110]</cite></a>.1463 it without a robust extension mechanism. In addition, it is used in a similar, but not identical fashion in MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. 1464 1464 </p> 1465 1465 <p id="rfc.section.C.1.p.3">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section 2.2</a>) … … 1493 1493 </li> 1494 1494 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46</a>>: "RFC1700 references" 1495 </li> 1496 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65</a>>: "Informative references" 1495 1497 </li> 1496 1498 <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66</a>>: "ISO-8859-1 Reference" … … 1671 1673 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> 1672 1674 <li class="indline1"><em>RFC1766</em> <a class="iref" href="#rfc.xref.RFC1766.1">2.5</a>, <a class="iref" href="#RFC1766"><b>9.3</b></a></li> 1673 <li class="indline1"><em>RFC1806</em> <a class="iref" href="#rfc.xref.RFC1806.1">7.2</a>, <a class="iref" href="#rfc.xref.RFC1806.2">7.2</a>, <a class="iref" href="#RFC1806"><b>9. 3</b></a>, <a class="iref" href="#rfc.xref.RFC1806.3">B.1</a></li>1675 <li class="indline1"><em>RFC1806</em> <a class="iref" href="#rfc.xref.RFC1806.1">7.2</a>, <a class="iref" href="#rfc.xref.RFC1806.2">7.2</a>, <a class="iref" href="#RFC1806"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC1806.3">B.1</a></li> 1674 1676 <li class="indline1"><em>RFC1864</em> <a class="iref" href="#rfc.xref.RFC1864.1">5.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">5.8</a>, <a class="iref" href="#RFC1864"><b>9.3</b></a></li> 1675 <li class="indline1"><em>RFC1867</em> <a class="iref" href="#rfc.xref.RFC1867.1">2.3.2</a>, <a class="iref" href="#RFC1867"><b>9.3</b></a></li> 1676 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> 1677 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> 1677 1678 <li class="indline1"><em>RFC1950</em> <a class="iref" href="#rfc.xref.RFC1950.1">2.2</a>, <a class="iref" href="#RFC1950"><b>9.1</b></a></li> 1678 1679 <li class="indline1"><em>RFC1951</em> <a class="iref" href="#rfc.xref.RFC1951.1">2.2</a>, <a class="iref" href="#RFC1951"><b>9.1</b></a></li> … … 1683 1684 </ul> 1684 1685 </li> 1685 <li class="indline1"><em>RFC2049</em> <a class="iref" href="#RFC2049"><b>9. 3</b></a>, <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a><ul class="ind">1686 <li class="indline1"><em>RFC2049</em> <a class="iref" href="#RFC2049"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a><ul class="ind"> 1686 1687 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a></li> 1687 1688 </ul> 1688 1689 </li> 1689 1690 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">§</a>, <a class="iref" href="#rfc.xref.RFC2068.2">§</a>, <a class="iref" href="#rfc.xref.RFC2068.3">§</a>, <a class="iref" href="#RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.4">B</a>, <a class="iref" href="#rfc.xref.RFC2068.5">C.1</a></li> 1690 <li class="indline1"><em>RFC2076</em> <a class="iref" href="#RFC2076"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li> 1691 <li class="indline1"><em>RFC2110</em> <a class="iref" href="#RFC2110"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2110.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2110.2">C.1</a></li> 1691 <li class="indline1"><em>RFC2076</em> <a class="iref" href="#RFC2076"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li> 1692 1692 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li> 1693 <li class="indline1"><em>RFC2183</em> <a class="iref" href="#rfc.xref.RFC2183.1">7.2</a>, <a class="iref" href="#RFC2183"><b>9.3</b></a></li> 1694 <li class="indline1"><em>RFC2277</em> <a class="iref" href="#rfc.xref.RFC2277.1">2.1</a>, <a class="iref" href="#RFC2277"><b>9.3</b></a></li> 1695 <li class="indline1"><em>RFC2279</em> <a class="iref" href="#rfc.xref.RFC2279.1">2.1</a>, <a class="iref" href="#RFC2279"><b>9.3</b></a></li> 1693 <li class="indline1"><em>RFC2183</em> <a class="iref" href="#rfc.xref.RFC2183.1">7.2</a>, <a class="iref" href="#RFC2183"><b>9.2</b></a></li> 1694 <li class="indline1"><em>RFC2277</em> <a class="iref" href="#rfc.xref.RFC2277.1">2.1</a>, <a class="iref" href="#RFC2277"><b>9.2</b></a></li> 1695 <li class="indline1"><em>RFC2388</em> <a class="iref" href="#rfc.xref.RFC2388.1">2.3.2</a>, <a class="iref" href="#RFC2388"><b>9.2</b></a></li> 1696 <li class="indline1"><em>RFC2557</em> <a class="iref" href="#RFC2557"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2557.2">C.1</a></li> 1696 1697 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li> 1698 <li class="indline1"><em>RFC3629</em> <a class="iref" href="#rfc.xref.RFC3629.1">2.1</a>, <a class="iref" href="#RFC3629"><b>9.2</b></a></li> 1697 1699 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC4288.2">2.3</a>, <a class="iref" href="#RFC4288"><b>9.3</b></a></li> 1698 <li class="indline1"><em>RFC822</em> <a class="iref" href="#RFC822"><b>9. 3</b></a>, <a class="iref" href="#rfc.xref.RFC822.1">A</a></li>1700 <li class="indline1"><em>RFC822</em> <a class="iref" href="#RFC822"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC822.1">A</a></li> 1699 1701 </ul> 1700 1702 </li>
Note: See TracChangeset
for help on using the changeset viewer.
