Changeset 369 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 13/11/08 19:41:14 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r368 r369 488 488 <t> 489 489 Historically, HTTP/1.1 header field values allow linear white space folding across 490 multiple lines. However, this specification deprecates its use; senders MUST NOT490 multiple lines. However, this specification deprecates its use; senders &MUST-NOT; 491 491 produce messages that include LWS folding (i.e., use the obs-fold rule), except 492 within the message/http media type <xref target="internet.media.type.message.http"/>. 493 Receivers SHOULD still parse folded linear white space. 494 </t> 495 <t> 496 This specification uses three rules to denote the use of linear white space; 497 BWS ("Bad" White Space), OWS (Optional White Space), and RWS (Required White Space). 498 </t> 499 <t> 500 "Bad" white space is allowed by the BNF, but senders SHOULD NOT produce it in messages. 501 Receivers MUST accept it in incoming messages. 502 </t> 503 492 within the message/http media type (<xref target="internet.media.type.message.http"/>). 493 Receivers &SHOULD; still parse folded linear white space. 494 </t> 495 <t> 496 This specification uses three rules to denote the use of linear white space; 497 BWS ("Bad" White Space), OWS (Optional White Space), and RWS (Required White Space). 498 </t> 499 <t> 500 "Bad" white space is allowed by the BNF, but senders &SHOULD-NOT; produce it in messages. 501 Receivers &MUST; accept it in incoming messages. 502 </t> 503 <t> 504 Required white space is used when at least one linear white space character 505 is required to separate field tokens. In all such cases, a single SP character 506 &SHOULD; be used. 507 </t> 504 508 <t anchor="rule.whitespace"> 505 509 <x:anchor-alias value="BWS"/> … … 507 511 <x:anchor-alias value="RWS"/> 508 512 <x:anchor-alias value="obs-fold"/> 509 510 513 </t> 511 514 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OWS"/><iref primary="true" item="Grammar" subitem="RWS"/><iref primary="true" item="Grammar" subitem="BWS"/> … … 517 520 ; "bad" white space 518 521 <x:ref>obs-fold</x:ref> = <x:ref>CRLF</x:ref> 519 ; <cref>to be explained: do not produce</cref>520 522 </artwork></figure> 521 523 <t anchor="rule.TEXT"> … … 528 530 </t> 529 531 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TEXT"/> 530 <x:ref>TEXT</x:ref> = %x20-7E / %x80-FF / <x:ref> LWS</x:ref>531 ; any <x:ref>OCTET</x:ref> except <x:ref>CTL</x:ref>s, but including <x:ref> LWS</x:ref>532 <x:ref>TEXT</x:ref> = %x20-7E / %x80-FF / <x:ref>OWS</x:ref> 533 ; any <x:ref>OCTET</x:ref> except <x:ref>CTL</x:ref>s, but including <x:ref>OWS</x:ref> 532 534 </artwork></figure> 533 535 <t> … … 1196 1198 <x:ref>message-header</x:ref> = <x:ref>field-name</x:ref> ":" [ <x:ref>field-value</x:ref> ] 1197 1199 <x:ref>field-name</x:ref> = <x:ref>token</x:ref> 1198 <x:ref>field-value</x:ref> = *( <x:ref>field-content</x:ref> / <x:ref> LWS</x:ref> )1200 <x:ref>field-value</x:ref> = *( <x:ref>field-content</x:ref> / <x:ref>OWS</x:ref> ) 1199 1201 <x:ref>field-content</x:ref> = <field content> 1200 1202 ; the <x:ref>OCTET</x:ref>s making up the field-value
Note: See TracChangeset
for help on using the changeset viewer.