* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 708


Ignore:
Timestamp:
2009-10-07 09:03:34 (5 years ago)
Author:
julian.reschke@gmx.de
Message:

Mention TRACE and OPTIONS as safe in prose (see #171)

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

Legend:

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

    r704 r708  
    399399      <meta name="DC.Creator" content="Reschke, J. F."> 
    400400      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 
    401       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-02"> 
     401      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-07"> 
    402402      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 
    403403      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> 
     
    436436         </tr> 
    437437         <tr> 
    438             <td class="header left">Expires: April 5, 2010</td> 
     438            <td class="header left">Expires: April 10, 2010</td> 
    439439            <td class="header right">H. Frystyk</td> 
    440440         </tr> 
     
    485485         <tr> 
    486486            <td class="header left"></td> 
    487             <td class="header right">October 2, 2009</td> 
     487            <td class="header right">October 7, 2009</td> 
    488488         </tr> 
    489489      </table> 
     
    509509      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;. 
    510510      </p> 
    511       <p>This Internet-Draft will expire in April 5, 2010.</p> 
     511      <p>This Internet-Draft will expire in April 10, 2010.</p> 
    512512      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    513513      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    937937         or others. 
    938938      </p> 
    939       <p id="rfc.section.7.1.1.p.2">In particular, the convention has been established that the GET and HEAD methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "<dfn id="safe">safe</dfn>". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is 
     939      <p id="rfc.section.7.1.1.p.2">In particular, the convention has been established that the GET, HEAD, OPTIONS, and TRACE methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "<dfn id="safe">safe</dfn>". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is 
    940940         made aware of the fact that a possibly unsafe action is being requested. 
    941941      </p> 
     
    25252525         </li> 
    25262526         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/198">http://tools.ietf.org/wg/httpbis/trac/ticket/198</a>&gt;: "move IANA registrations for optional status codes" 
     2527         </li> 
     2528      </ul> 
     2529      <p id="rfc.section.C.9.p.2">Partly resolved issues: </p> 
     2530      <ul> 
     2531         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/171">http://tools.ietf.org/wg/httpbis/trac/ticket/171</a>&gt;: "Are OPTIONS and TRACE safe?" 
    25272532         </li> 
    25282533      </ul> 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r704 r708  
    720720</t> 
    721721<t> 
    722    In particular, the convention has been established that the GET and 
    723    HEAD methods &SHOULD-NOT;  have the significance of taking an action 
     722   In particular, the convention has been established that the GET, HEAD, 
     723   OPTIONS, and TRACE methods &SHOULD-NOT;  have the significance of taking an action 
    724724   other than retrieval. These methods ought to be considered "<x:dfn anchor="safe">safe</x:dfn>". 
    725725   This allows user agents to represent other methods, such as POST, PUT 
     
    37023702  </list> 
    37033703</t> 
     3704<t> 
     3705  Partly resolved issues: 
     3706  <list style="symbols">  
     3707    <t> 
     3708      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/171"/>: 
     3709      "Are OPTIONS and TRACE safe?" 
     3710    </t> 
     3711  </list> 
     3712</t> 
     3713 
    37043714</section> 
    37053715 
Note: See TracChangeset for help on using the changeset viewer.