Changeset 2480
- Timestamp:
- 07/11/13 15:28:22 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2477 r2480 445 445 } 446 446 @bottom-center { 447 content: "Expires May 9, 2014";447 content: "Expires May 11, 2014"; 448 448 } 449 449 @bottom-right { … … 487 487 <meta name="dct.creator" content="Reschke, J. F."> 488 488 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 489 <meta name="dct.issued" scheme="ISO8601" content="2013-11-0 5">489 <meta name="dct.issued" scheme="ISO8601" content="2013-11-07"> 490 490 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 491 491 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 516 516 <tr> 517 517 <td class="left">Intended status: Standards Track</td> 518 <td class="right">November 5, 2013</td>518 <td class="right">November 7, 2013</td> 519 519 </tr> 520 520 <tr> 521 <td class="left">Expires: May 9, 2014</td>521 <td class="left">Expires: May 11, 2014</td> 522 522 <td class="right"></td> 523 523 </tr> … … 548 548 in progress”. 549 549 </p> 550 <p>This Internet-Draft will expire on May 9, 2014.</p>550 <p>This Internet-Draft will expire on May 11, 2014.</p> 551 551 </div> 552 552 <div id="rfc.copyrightnotice"> … … 1514 1514 </p> 1515 1515 <p id="rfc.section.3.3.2.p.11">Any Content-Length field value greater than or equal to zero is valid. Since there is no predefined limit to the length of 1516 a payload, a recipient <em class="bcp14"> SHOULD</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows (<a href="#attack.protocol.element.size.overflows" title="Buffer Overflows">Section 9.3</a>).1516 a payload, a recipient <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows (<a href="#attack.protocol.element.size.overflows" title="Buffer Overflows">Section 9.3</a>). 1517 1517 </p> 1518 1518 <p id="rfc.section.3.3.2.p.12">If a message is received that has multiple Content-Length header fields with field-values consisting of the same decimal value, … … 3427 3427 <ul> 3428 3428 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/502">http://tools.ietf.org/wg/httpbis/trac/ticket/502</a>>: "APPSDIR review of draft-ietf-httpbis-p1-messaging-24" 3429 </li> 3430 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/507">http://tools.ietf.org/wg/httpbis/trac/ticket/507</a>>: "integer value parsing" 3429 3431 </li> 3430 3432 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/517">http://tools.ietf.org/wg/httpbis/trac/ticket/517</a>>: "move IANA registrations to correct draft" -
draft-ietf-httpbis/latest/p1-messaging.xml
r2477 r2480 1711 1711 Any Content-Length field value greater than or equal to zero is valid. 1712 1712 Since there is no predefined limit to the length of a payload, a 1713 recipient & SHOULD; anticipate potentially large decimal numerals and1713 recipient &MUST; anticipate potentially large decimal numerals and 1714 1714 prevent parsing errors due to integer conversion overflows 1715 1715 (<xref target="attack.protocol.element.size.overflows"/>). … … 5414 5414 </t> 5415 5415 <t> 5416 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/507"/>: 5417 "integer value parsing" 5418 </t> 5419 <t> 5416 5420 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/517"/>: 5417 5421 "move IANA registrations to correct draft" -
draft-ietf-httpbis/latest/p5-range.html
r2477 r2480 445 445 } 446 446 @bottom-center { 447 content: "Expires May 9, 2014";447 content: "Expires May 11, 2014"; 448 448 } 449 449 @bottom-right { … … 488 488 <meta name="dct.creator" content="Reschke, J. F."> 489 489 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 490 <meta name="dct.issued" scheme="ISO8601" content="2013-11-0 5">490 <meta name="dct.issued" scheme="ISO8601" content="2013-11-07"> 491 491 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 492 492 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests."> … … 514 514 </tr> 515 515 <tr> 516 <td class="left">Expires: May 9, 2014</td>516 <td class="left">Expires: May 11, 2014</td> 517 517 <td class="right">J. Reschke, Editor</td> 518 518 </tr> … … 523 523 <tr> 524 524 <td class="left"></td> 525 <td class="right">November 5, 2013</td>525 <td class="right">November 7, 2013</td> 526 526 </tr> 527 527 </tbody> … … 549 549 in progress”. 550 550 </p> 551 <p>This Internet-Draft will expire on May 9, 2014.</p>551 <p>This Internet-Draft will expire on May 11, 2014.</p> 552 552 </div> 553 553 <div id="rfc.copyrightnotice"> … … 718 718 <p id="rfc.section.2.1.p.13">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable. 719 719 </p> 720 <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought 721 to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows. 720 <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows. 722 721 </p> 723 722 </div> … … 1380 1379 <ul> 1381 1380 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/506">http://tools.ietf.org/wg/httpbis/trac/ticket/506</a>>: "APPSDIR review of draft-ietf-httpbis-p5-range-24" 1381 </li> 1382 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/507">http://tools.ietf.org/wg/httpbis/trac/ticket/507</a>>: "integer value parsing" 1382 1383 </li> 1383 1384 <li><<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/508">http://tools.ietf.org/wg/httpbis/trac/ticket/508</a>>: "broken sentence in description of 206" -
draft-ietf-httpbis/latest/p5-range.xml
r2477 r2480 314 314 <x:ref>last-byte-pos</x:ref>, and <x:ref>suffix-length</x:ref> are 315 315 expressed as decimal number of octets. Since there is no predefined limit 316 to the length of a payload, recipients ought toanticipate potentially316 to the length of a payload, recipients &MUST; anticipate potentially 317 317 large decimal numerals and prevent parsing errors due to integer conversion 318 318 overflows. … … 1514 1514 </t> 1515 1515 <t> 1516 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/507"/>: 1517 "integer value parsing" 1518 </t> 1519 <t> 1516 1520 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/508"/>: 1517 1521 "broken sentence in description of 206"
Note: See TracChangeset
for help on using the changeset viewer.