Ignore:
Timestamp:
Sep 18, 2012, 12:53:38 AM (7 years ago)
Author:
fielding@…
Message:

https requires and end-to-end secured connection. Addresses #383

Refer just to TLS, not SSL/TLS.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1901 r1903  
    886886   An HTTP service based on some other underlying connection protocol
    887887   would presumably be identified using a different URI scheme, just as
    888    the "https" scheme (below) is used for servers that require an SSL/TLS
    889    transport layer on a connection. Other protocols might also be used to
     888   the "https" scheme (below) is used for resources that require an
     889   end-to-end secured connection. Other protocols might also be used to
    890890   provide access to "http" identified resources — it is only the
    891891   authoritative interface used for mapping the namespace that is
     
    916916   The "https" URI scheme is hereby defined for the purpose of minting
    917917   identifiers according to their association with the hierarchical
    918    namespace governed by a potential HTTP origin server listening for
    919    SSL/TLS-secured connections on a given TCP port.
     918   namespace governed by a potential HTTP origin server listening to a
     919   given TCP port for TLS-secured connections <xref target="RFC5246"/>.
    920920</t>
    921921<t>
     
    923923   requirements for the "https" scheme, except that a default TCP port
    924924   of 443 is assumed if the port subcomponent is empty or not given,
    925    and the TCP connection &MUST; be secured through the
     925   and the TCP connection &MUST; be secured, end-to-end, through the
    926926   use of strong encryption prior to sending the first HTTP request.
    927927</t>
     
    23622362</t>
    23632363<t>
    2364    If the request is received over an SSL/TLS-secured TCP connection,
     2364   If the request is received over a TLS-secured TCP connection,
    23652365   then the effective request URI's scheme is "https"; otherwise, the
    23662366   scheme is "http".
     
    24052405<figure>
    24062406<preamble>
    2407    Example 2: the following message received over an SSL/TLS-secured TCP
    2408    connection
     2407   Example 2: the following message received over a TLS-secured TCP connection
    24092408</preamble>
    24102409<artwork type="example" x:indent-with="  ">
Note: See TracChangeset for help on using the changeset viewer.