Changeset 1101 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 08/01/11 14:27:21 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1099 r1101 15 15 <!ENTITY ID-MONTH "January"> 16 16 <!ENTITY ID-YEAR "2011"> 17 <!ENTITY mdash "—"> 17 18 <!ENTITY caching-overview "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 19 <!ENTITY cache-incomplete "<xref target='Part6' x:rel='#errors.or.incomplete.response.cache.behavior' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 961 962 the "https" scheme (below) is used for servers that require an SSL/TLS 962 963 transport layer on a connection. Other protocols might also be used to 963 provide access to "http" identified resources ---it is only the964 provide access to "http" identified resources — it is only the 964 965 authoritative interface used for mapping the namespace that is 965 966 specific to TCP. … … 3569 3570 </t> 3570 3571 <t hangText="msgtype:"> 3571 The message type --"request" or "response". If not3572 The message type — "request" or "response". If not 3572 3573 present, the type can be determined from the first 3573 3574 line of the body. … … 3638 3639 </t> 3639 3640 <t hangText="msgtype:"> 3640 The message type --"request" or "response". If not3641 The message type — "request" or "response". If not 3641 3642 present, the type can be determined from the first 3642 3643 line of the body. … … 3725 3726 <section title="Upgrade Token Registration" anchor="upgrade.token.registration"> 3726 3727 <t> 3727 The registration procedure for HTTP Upgrade Tokens --previously defined3728 in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/> --is now defined3728 The registration procedure for HTTP Upgrade Tokens — previously defined 3729 in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/> — is now defined 3729 3730 by <xref target="upgrade.token.registry"/> of this document. 3730 3731 </t> … … 3895 3896 <t> 3896 3897 HTTP has evolved considerably over the years. It has 3897 benefited from a large and active developer community --the many3898 people who have participated on the www-talk mailing list --and it is3898 benefited from a large and active developer community — the many 3899 people who have participated on the www-talk mailing list — and it is 3899 3900 that community which has been most responsible for the success of 3900 3901 HTTP and of the World-Wide Web in general. Marc Andreessen, Robert … … 5267 5268 <t> 5268 5269 Add rules for terms imported from URI spec ("absoluteURI", "authority", 5269 "path-absolute", "port", "query", "relativeURI", "host) --these will5270 "path-absolute", "port", "query", "relativeURI", "host) — these will 5270 5271 have to be updated when switching over to RFC3986. 5271 5272 </t>
Note: See TracChangeset
for help on using the changeset viewer.