Changeset 969 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 31/07/10 01:06:01 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r968 r969 729 729 <iref item="Safe Methods" primary="true"/> 730 730 <t> 731 Implementors shouldbe aware that the software represents the user in732 their interactions over the Internet, and should be carefulto allow731 Implementors need to be aware that the software represents the user in 732 their interactions over the Internet, and need to allow 733 733 the user to be aware of any actions they take which might have an 734 734 unexpected significance to themselves or others. … … 1329 1329 <x:h>Note:</x:h> An earlier version of this specification recommended a 1330 1330 maximum of five redirections (<xref target="RFC2068" x:fmt="," x:sec="10.3"/>). 1331 Content developers should be aware that there might be clients that1331 Content developers need to be aware that some clients might 1332 1332 implement such a fixed limitation. 1333 1333 </t> … … 2179 2179 obsolete or mistyped links to be traced for maintenance. Some servers use 2180 2180 Referer as a means of controlling where they allow links from (so-called 2181 "deep linking"), but it should be noted that legitimate requests are not2182 required tocontain a Referer header field.2181 "deep linking"), but legitimate requests do not always 2182 contain a Referer header field. 2183 2183 </t> 2184 2184 <t> … … 2329 2329 </t> 2330 2330 <t> 2331 The HTTP Method Registry sh ouldbe created at <eref target="http://www.iana.org/assignments/http-methods"/>2331 The HTTP Method Registry shall be created at <eref target="http://www.iana.org/assignments/http-methods"/> 2332 2332 and be populated with the registrations below: 2333 2333 </t> … … 2391 2391 <t> 2392 2392 The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/> 2393 sh ouldbe updated with the registrations below:2393 shall be updated with the registrations below: 2394 2394 </t> 2395 2395 <?BEGININC p2-semantics.iana-status-codes ?> … … 2585 2585 <section title="Header Field Registration" anchor="header.field.registration"> 2586 2586 <t> 2587 The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> sh ouldbe updated2587 The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated 2588 2588 with the permanent registrations below (see <xref target="RFC3864"/>): 2589 2589 </t> … … 2744 2744 </t> 2745 2745 <t> 2746 Authors of services should notuse GET-based forms for the submission of2747 sensitive data because that data will be encoded in the request-target. Many2746 Authors of services &SHOULD-NOT; use GET-based forms for the submission of 2747 sensitive data because that data will be placed in the request-target. Many 2748 2748 existing servers, proxies, and user agents log or display the request-target 2749 2749 in places where it might be visible to third parties. Such services can
Note: See TracChangeset
for help on using the changeset viewer.