Changeset 1692 for draft-ietf-httpbis/latest/p4-conditional.xml
- Timestamp:
- 23/06/12 12:01:38 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.xml
r1691 r1692 15 15 <!ENTITY ID-MONTH "June"> 16 16 <!ENTITY ID-YEAR "2012"> 17 <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>"> 17 18 <!ENTITY architecture "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 19 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 484 485 <x:note> 485 486 <t> 486 <x:h>Note:</x:h>Previously, opaque-tag was defined to be a quoted-string487 &Note; Previously, opaque-tag was defined to be a quoted-string 487 488 (<xref target="RFC2616" x:fmt="," x:sec="3.11"/>), thus some recipients 488 489 might perform backslash unescaping. Servers therefore ought to avoid … … 635 636 <x:note> 636 637 <t> 637 <x:h>Note:</x:h>Content codings are a property of the representation,638 &Note; Content codings are a property of the representation, 638 639 so therefore an entity-tag of an encoded representation has to be distinct 639 640 from an unencoded representation to prevent conflicts during cache updates … … 706 707 conditional header fields in the request. 707 708 <list><t> 708 <x:h>Note:</x:h>The general principle behind these rules is that HTTP/1.1709 &Note; The general principle behind these rules is that HTTP/1.1 709 710 servers and clients ought to transmit as much non-redundant 710 711 information as is available in their responses and requests. … … 897 898 information with a minimum amount of transaction overhead. 898 899 <list><t> 899 <x:h>Note:</x:h>The Range header field modifies the meaning of If-Modified-Since;900 &Note; The Range header field modifies the meaning of If-Modified-Since; 900 901 see &header-range; for full details. 901 902 </t><t> 902 <x:h>Note:</x:h>If-Modified-Since times are interpreted by the server, whose903 &Note; If-Modified-Since times are interpreted by the server, whose 903 904 clock might not be synchronized with the client. 904 905 </t><t> 905 <x:h>Note:</x:h>When handling an If-Modified-Since header field, some906 &Note; When handling an If-Modified-Since header field, some 906 907 servers will use an exact date comparison function, rather than a 907 908 less-than function, for deciding whether to send a 304 (Not … … 911 912 header field whenever possible. 912 913 </t><t> 913 <x:h>Note:</x:h>If a client uses an arbitrary date in the If-Modified-Since914 &Note; If a client uses an arbitrary date in the If-Modified-Since 914 915 header field instead of a date taken from the Last-Modified header field for 915 916 the same request, the client needs to be aware that this
Note: See TracChangeset
for help on using the changeset viewer.