Ignore:
Timestamp:
28/01/14 08:25:27 (6 years ago)
Author:
fielding@…
Message:

(editorial) remove a redundant reference to improve readability; see #531

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r2597 r2598  
    11381138               <div id="rfc.iref.u.4"></div>
    11391139               <p id="rfc.section.2.7.2.p.1">The "https" URI scheme is hereby defined for the purpose of minting identifiers according to their association with the hierarchical
    1140                   namespace governed by a potential HTTP origin server listening to a given TCP port for TLS-secured connections (<a href="#RFC0793" id="rfc.xref.RFC0793.2"><cite title="Transmission Control Protocol">[RFC0793]</cite></a>, <a href="#RFC5246" id="rfc.xref.RFC5246.2"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>).
    1141                </p>
    1142                <p id="rfc.section.2.7.2.p.2">All of the requirements listed above for the "http" scheme are also requirements for the "https" scheme, except that a default
    1143                   TCP port of 443 is assumed if the port subcomponent is empty or not given, and the user agent <em class="bcp14">MUST</em> ensure that its connection to the origin server is secured through the use of strong encryption, end-to-end, prior to sending
     1140                  namespace governed by a potential HTTP origin server listening to a given TCP port for TLS-secured connections (<a href="#RFC5246" id="rfc.xref.RFC5246.2"><cite title="The Transport Layer Security (TLS) Protocol Version 1.2">[RFC5246]</cite></a>).
     1141               </p>
     1142               <p id="rfc.section.2.7.2.p.2">All of the requirements listed above for the "http" scheme are also requirements for the "https" scheme, except that TCP port
     1143                  443 is the default if the port subcomponent is empty or not given, and the user agent <em class="bcp14">MUST</em> ensure that its connection to the origin server is secured through the use of strong encryption, end-to-end, prior to sending
    11441144                  the first HTTP request.
    11451145               </p>
     
    36973697                  <li>response&nbsp;&nbsp;<a href="#rfc.iref.r.3"><b>2.1</b></a></li>
    36983698                  <li>reverse proxy&nbsp;&nbsp;<a href="#rfc.iref.r.4"><b>2.3</b></a></li>
    3699                   <li><em>RFC0793</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC0793.1">2.7.1</a>, <a href="#rfc.xref.RFC0793.2">2.7.2</a>, <a href="#RFC0793"><b>11.1</b></a></li>
     3699                  <li><em>RFC0793</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC0793.1">2.7.1</a>, <a href="#RFC0793"><b>11.1</b></a></li>
    37003700                  <li><em>RFC1919</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1919.1">2.3</a>, <a href="#RFC1919"><b>11.2</b></a></li>
    37013701                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">2.6</a>, <a href="#rfc.xref.RFC1945.2">10</a>, <a href="#RFC1945"><b>11.2</b></a>, <a href="#rfc.xref.RFC1945.3">A</a></li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2597 r2598  
    949949   identifiers according to their association with the hierarchical
    950950   namespace governed by a potential HTTP origin server listening to a
    951    given TCP port for TLS-secured connections
    952    (<xref target="RFC0793"/>, <xref target="RFC5246"/>).
     951   given TCP port for TLS-secured connections (<xref target="RFC5246"/>).
    953952</t>
    954953<t>
    955954   All of the requirements listed above for the "http" scheme are also
    956    requirements for the "https" scheme, except that a default TCP port
    957    of 443 is assumed if the port subcomponent is empty or not given,
     955   requirements for the "https" scheme, except that TCP port 443 is the
     956   default if the port subcomponent is empty or not given,
    958957   and the user agent &MUST; ensure that its connection to the origin
    959958   server is secured through the use of strong encryption, end-to-end,
Note: See TracChangeset for help on using the changeset viewer.