Changeset 2278 for draft-ietf-httpbis/latest
- Timestamp:
- 03/06/13 07:15:20 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2277 r2278 1075 1075 would presumably be identified using a different URI scheme, just as the "https" scheme (below) is used for resources that 1076 1076 require an end-to-end secured connection. Other protocols might also be used to provide access to "http" identified resources 1077 — it is only the authoritative interface used for mapping the namespacethat is specific to TCP.1077 — it is only the authoritative interface that is specific to TCP. 1078 1078 </p> 1079 1079 <p id="rfc.section.2.7.1.p.8">The URI generic syntax for authority also includes a deprecated userinfo subcomponent (<a href="#RFC3986" id="rfc.xref.RFC3986.13"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-3.2.1">Section 3.2.1</a>) for including user authentication information in the URI. Some implementations make use of the userinfo component for internal … … 1093 1093 </p> 1094 1094 <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.26"></span> <a href="#https.uri" class="smpl">https-URI</a> = "https:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ] 1095 </pre><p id="rfc.section.2.7.2.p.4"> Resources made available via the "https" scheme have no shared identity with the "http" scheme even if their resource identifiers1096 indicate the same authority (the same host listening to the same TCP port). They are distinct name spaces and are considered1097 to be distinct origin servers. However, an extension to HTTP that is defined to apply to entire host domains, such as the1098 Cookie protocol <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>, can allow information set by one service to impact communication with other services within a matching group of host domains.1095 </pre><p id="rfc.section.2.7.2.p.4">Note that the "https" URI scheme depends on both TLS and TCP for establishing authority. Resources made available via the 1096 "https" scheme have no shared identity with the "http" scheme even if their resource identifiers indicate the same authority 1097 (the same host listening to the same TCP port). They are distinct name spaces and are considered to be distinct origin servers. 1098 However, an extension to HTTP that is defined to apply to entire host domains, such as the Cookie protocol <a href="#RFC6265" id="rfc.xref.RFC6265.1"><cite title="HTTP State Management Mechanism">[RFC6265]</cite></a>, can allow information set by one service to impact communication with other services within a matching group of host domains. 1099 1099 </p> 1100 1100 <p id="rfc.section.2.7.2.p.5">The process for authoritative access to an "https" identified resource is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.2"><cite title="HTTP Over TLS">[RFC2818]</cite></a>. -
draft-ietf-httpbis/latest/p1-messaging.xml
r2277 r2278 893 893 end-to-end secured connection. Other protocols might also be used to 894 894 provide access to "http" identified resources — it is only the 895 authoritative interface used for mapping the namespace that is 896 specific to TCP. 895 authoritative interface that is specific to TCP. 897 896 </t> 898 897 <t> … … 935 934 </artwork></figure> 936 935 <t> 936 Note that the "https" URI scheme depends on both TLS and TCP for 937 establishing authority. 937 938 Resources made available via the "https" scheme have no shared 938 939 identity with the "http" scheme even if their resource identifiers
Note: See TracChangeset
for help on using the changeset viewer.