Changeset 1384 for draft-ietf-httpbis
- Timestamp:
- 06/08/11 11:12:57 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1377 r1384 359 359 } 360 360 @bottom-center { 361 content: "Expires February 5, 2012";361 content: "Expires February 7, 2012"; 362 362 } 363 363 @bottom-right { … … 410 410 <meta name="dct.creator" content="Reschke, J. F."> 411 411 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 412 <meta name="dct.issued" scheme="ISO8601" content="2011-08-0 4">412 <meta name="dct.issued" scheme="ISO8601" content="2011-08-06"> 413 413 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 414 414 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 442 442 </tr> 443 443 <tr> 444 <td class="left">Expires: February 5, 2012</td>444 <td class="left">Expires: February 7, 2012</td> 445 445 <td class="right">HP</td> 446 446 </tr> … … 495 495 <tr> 496 496 <td class="left"></td> 497 <td class="right">August 4, 2011</td>497 <td class="right">August 6, 2011</td> 498 498 </tr> 499 499 </tbody> … … 528 528 in progress”. 529 529 </p> 530 <p>This Internet-Draft will expire on February 5, 2012.</p>530 <p>This Internet-Draft will expire on February 7, 2012.</p> 531 531 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 532 532 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 826 826 </p> 827 827 </div> 828 <p id="rfc.section.1.2.2.p.3">The OWS rule is used where zero or more linear whitespace octets might appear. OWS <em class="bcp14">SHOULD</em> either not be produced or be produced as a single SP. Multiple OWS octets that occur within field-content <em class="bcp14">SHOULD</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream. 829 </p> 830 <p id="rfc.section.1.2.2.p.4">RWS is used when at least one linear whitespace octet is required to separate field tokens. RWS <em class="bcp14">SHOULD</em> be produced as a single SP. Multiple RWS octets that occur within field-content <em class="bcp14">SHOULD</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream. 831 </p> 832 <p id="rfc.section.1.2.2.p.5">BWS is used where the grammar allows optional whitespace for historical reasons but senders <em class="bcp14">SHOULD NOT</em> produce it in messages. HTTP/1.1 recipients <em class="bcp14">MUST</em> accept such bad optional whitespace and remove it before interpreting the field value or forwarding the message downstream. 833 </p> 828 <div id="rule.OWS"> 829 <p id="rfc.section.1.2.2.p.3">The OWS rule is used where zero or more linear whitespace octets might appear. OWS <em class="bcp14">SHOULD</em> either not be produced or be produced as a single SP. Multiple OWS octets that occur within field-content <em class="bcp14">SHOULD</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream. 830 </p> 831 </div> 832 <div id="rule.RWS"> 833 <p id="rfc.section.1.2.2.p.4">RWS is used when at least one linear whitespace octet is required to separate field tokens. RWS <em class="bcp14">SHOULD</em> be produced as a single SP. Multiple RWS octets that occur within field-content <em class="bcp14">SHOULD</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream. 834 </p> 835 </div> 836 <div id="rule.BWS"> 837 <p id="rfc.section.1.2.2.p.5">BWS is used where the grammar allows optional whitespace for historical reasons but senders <em class="bcp14">SHOULD NOT</em> produce it in messages. HTTP/1.1 recipients <em class="bcp14">MUST</em> accept such bad optional whitespace and remove it before interpreting the field value or forwarding the message downstream. 838 </p> 839 </div> 834 840 <div id="rule.whitespace"> 835 841 <p id="rfc.section.1.2.2.p.6"> </p> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1377 r1384 441 441 BWS ("bad" whitespace). 442 442 </t> 443 <t >443 <t anchor="rule.OWS"> 444 444 The OWS rule is used where zero or more linear whitespace octets might 445 445 appear. OWS &SHOULD; either not be produced or be produced as a single … … 448 448 forwarding the message downstream. 449 449 </t> 450 <t >450 <t anchor="rule.RWS"> 451 451 RWS is used when at least one linear whitespace octet is required to 452 452 separate field tokens. RWS &SHOULD; be produced as a single SP. … … 455 455 forwarding the message downstream. 456 456 </t> 457 <t >457 <t anchor="rule.BWS"> 458 458 BWS is used where the grammar allows optional whitespace for historical 459 459 reasons but senders &SHOULD-NOT; produce it in messages. HTTP/1.1
Note: See TracChangeset
for help on using the changeset viewer.