Changeset 1684 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- 22/06/12 07:12:17 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r1682 r1684 449 449 } 450 450 @bottom-center { 451 content: "Expires December 2 3, 2012";451 content: "Expires December 24, 2012"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 1">494 <meta name="dct.issued" scheme="ISO8601" content="2012-06-22"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 496 496 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range requests and the rules for constructing and combining responses to those requests."> … … 518 518 </tr> 519 519 <tr> 520 <td class="left">Expires: December 2 3, 2012</td>520 <td class="left">Expires: December 24, 2012</td> 521 521 <td class="right">J. Reschke, Editor</td> 522 522 </tr> … … 527 527 <tr> 528 528 <td class="left"></td> 529 <td class="right">June 2 1, 2012</td>529 <td class="right">June 22, 2012</td> 530 530 </tr> 531 531 </tbody> … … 555 555 in progress”. 556 556 </p> 557 <p>This Internet-Draft will expire on December 2 3, 2012.</p>557 <p>This Internet-Draft will expire on December 24, 2012.</p> 558 558 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 559 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 682 682 <p id="rfc.section.1.1.p.5">Unless noted otherwise, Recipients <em class="bcp14">MUST</em> be able to parse all protocol elements matching the ABNF rules defined for them and <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling 683 683 mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require 684 different error handling strategies; for example, a Web browser m ay wish to transparently recover from a response where the685 Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type of686 error recovery could lead to dangerous consequences.684 different error handling strategies; for example, a Web browser might wish to transparently recover from a response where 685 the Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type 686 of error recovery could lead to dangerous consequences. 687 687 </p> 688 688 <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a id="notation" href="#notation">Syntax Notation</a></h2>
Note: See TracChangeset
for help on using the changeset viewer.