Ignore:
Timestamp:
Jan 22, 2008, 6:11:10 PM (12 years ago)
Author:
fielding@…
Message:

editorial: replace redundant "the HTTP protocol" phrases or rephrase

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r170 r172  
    13421342      <div id="rfc.iref.s.41"></div>
    13431343      <h3 id="rfc.section.9.5.6"><a href="#rfc.section.9.5.6">9.5.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    1344       <p id="rfc.section.9.5.6.p.1">The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server
     1344      <p id="rfc.section.9.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
    13451345         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    13461346         in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server.
     
    15461546      <p id="rfc.section.12.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
    15471547      </p>
    1548       <p id="rfc.section.12.2.p.3">Authors of services which use the HTTP protocol <em class="bcp14">SHOULD NOT</em> use GET based forms for the submission of sensitive data, because this will cause this data to be encoded in the Request-URI.
    1549          Many existing servers, proxies, and user agents will log the request URI in some place where it might be visible to third
    1550          parties. Servers can use POST-based form submission instead
     1548      <p id="rfc.section.12.2.p.3">Authors of services should not use GET-based forms for the submission of sensitive data because that data will be encoded
     1549         in the Request-URI. Many existing servers, proxies, and user agents log or display the Request-URI in places where it might
     1550         be visible to third parties. Such services can use POST-based form submission instead.
    15511551      </p>
    15521552      <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;<a id="location.spoofing" href="#location.spoofing">Location Headers and Spoofing</a></h2>
Note: See TracChangeset for help on using the changeset viewer.