Changeset 760


Ignore:
Timestamp:
Feb 12, 2010, 8:31:30 AM (10 years ago)
Author:
julian.reschke@…
Message:

Replace "GET or HEAD" by "safe method" in intro to 3xx codes (fix typo) (see #10)

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

Legend:

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

    r759 r760  
    12081208      <p id="rfc.section.8.3.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.
    12091209         The action required <em class="bcp14">MAY</em> be carried out by the user agent without interaction with the user if and only if the method used in the second request is
    1210          is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
     1210         known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
    12111211      </p>
    12121212      <div class="note" id="rfc.section.8.3.p.2">
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r759 r760  
    12821282   required &MAY; be carried out by the user agent without interaction
    12831283   with the user if and only if the method used in the second request is
    1284    is known to be "safe", as defined in <xref target="safe.methods"/>.
     1284   known to be "safe", as defined in <xref target="safe.methods"/>.
    12851285   A client &SHOULD; detect infinite redirection loops, since such loops
    12861286   generate network traffic for each redirection.
Note: See TracChangeset for help on using the changeset viewer.