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.xml

    r170 r172  
    16271627  <iref primary="true" item="Status Codes" subitem="505 HTTP Version Not Supported" x:for-anchor=""/>
    16281628<t>
    1629    The server does not support, or refuses to support, the HTTP protocol
     1629   The server does not support, or refuses to support, the protocol
    16301630   version that was used in the request message. The server is
    16311631   indicating that it is unable or unwilling to complete the request
     
    20552055</t>
    20562056<t>
    2057    Clients &SHOULD-NOT;  include a Referer header field in a (non-secure)
     2057   Clients &SHOULD-NOT; include a Referer header field in a (non-secure)
    20582058   HTTP request if the referring page was transferred with a secure
    20592059   protocol.
    20602060</t>
    20612061<t>
    2062    Authors of services which use the HTTP protocol &SHOULD-NOT;  use GET
    2063    based forms for the submission of sensitive data, because this will
    2064    cause this data to be encoded in the Request-URI. Many existing
    2065    servers, proxies, and user agents will log the request URI in some
    2066    place where it might be visible to third parties. Servers can use
    2067    POST-based form submission instead
     2062   Authors of services should not use
     2063   GET-based forms for the submission of sensitive data because that
     2064   data will be encoded in the Request-URI. Many existing
     2065   servers, proxies, and user agents log or display the Request-URI in
     2066   places where it might be visible to third parties. Such services can
     2067   use POST-based form submission instead.
    20682068</t>
    20692069</section>
Note: See TracChangeset for help on using the changeset viewer.