Changeset 172 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 23/01/08 02:11:10 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r170 r172 1627 1627 <iref primary="true" item="Status Codes" subitem="505 HTTP Version Not Supported" x:for-anchor=""/> 1628 1628 <t> 1629 The server does not support, or refuses to support, the HTTPprotocol1629 The server does not support, or refuses to support, the protocol 1630 1630 version that was used in the request message. The server is 1631 1631 indicating that it is unable or unwilling to complete the request … … 2055 2055 </t> 2056 2056 <t> 2057 Clients &SHOULD-NOT; 2057 Clients &SHOULD-NOT; include a Referer header field in a (non-secure) 2058 2058 HTTP request if the referring page was transferred with a secure 2059 2059 protocol. 2060 2060 </t> 2061 2061 <t> 2062 Authors of services which use the HTTP protocol &SHOULD-NOT; use GET2063 based forms for the submission of sensitive data, because this will2064 cause this data tobe encoded in the Request-URI. Many existing2065 servers, proxies, and user agents will log the request URI in some2066 place where it might be visible to third parties. Servers can use2067 POST-based form submission instead2062 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. 2068 2068 </t> 2069 2069 </section>
Note: See TracChangeset
for help on using the changeset viewer.