Ignore:
Timestamp:
Jul 24, 2010, 12:25:07 AM (9 years ago)
Author:
fielding@…
Message:

(editorial) use might instead of may where it might be confused with MAY

File:
1 edited

Legend:

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

    r898 r901  
    703703   <t>If the response has a Content-Location header, and that URI is not the
    704704   same as the Effective Request URI, the response asserts that it is a
    705    representation of the resource at the Content-Location URI (but it may not
     705   representation of the resource at the Content-Location URI (but it might not
    706706   be).</t>
    707707   <t>Otherwise, the response is a representation of an anonymous (i.e.,
     
    732732   Implementors should be aware that the software represents the user in
    733733   their interactions over the Internet, and should be careful to allow
    734    the user to be aware of any actions they might take which may have an
     734   the user to be aware of any actions they take which might have an
    735735   unexpected significance to themselves or others.
    736736</t>
    737737<t>
    738738   In particular, the convention has been established that the GET, HEAD,
    739    OPTIONS, and TRACE methods &SHOULD-NOT;  have the significance of taking an action
     739   OPTIONS, and TRACE methods &SHOULD-NOT; have the significance of taking an action
    740740   other than retrieval. These methods ought to be considered "<x:dfn anchor="safe">safe</x:dfn>".
    741741   This allows user agents to represent other methods, such as POST, PUT
     
    14671467   transferred by the server over HTTP.  The Location URI indicates a
    14681468   resource that is descriptive of the requested resource such that
    1469    the follow-on representation may be useful without implying that
     1469   the follow-on representation might be useful without implying that
    14701470   it adequately represents the previously requested resource.
    14711471   Note that answers to the questions of what can be represented, what
     
    15541554   input connection. If the client continues sending data to the server
    15551555   after the close, the server's TCP stack will send a reset packet to
    1556    the client, which may erase the client's unacknowledged input buffers
     1556   the client, which might erase the client's unacknowledged input buffers
    15571557   before they can be read and interpreted by the HTTP application.
    15581558</t>
     
    16491649    <x:h>Note:</x:h> HTTP/1.1 servers are allowed to return responses which are
    16501650    not acceptable according to the accept headers sent in the
    1651     request. In some cases, this may even be preferable to sending a
     1651    request. In some cases, this might even be preferable to sending a
    16521652    406 response. User agents are encouraged to inspect the headers of
    16531653    an incoming response to determine if it is acceptable.
     
    18811881  <t>
    18821882    <x:h>Note:</x:h> The existence of the 503 status code does not imply that a
    1883     server must use it when becoming overloaded. Some servers may wish
     1883    server must use it when becoming overloaded. Some servers might wish
    18841884    to simply refuse the connection.
    18851885  </t>
     
    21472147<t>
    21482148   The Max-Forwards value is a decimal integer indicating the remaining
    2149    number of times this request message may be forwarded.
     2149   number of times this request message can be forwarded.
    21502150</t>
    21512151<t>
     
    27212721</t>
    27222722<t>
    2723    Some methods, like TRACE (<xref target="TRACE"/>) may expose
    2724    information sent in request headers in the response.
     2723   Some methods, like TRACE (<xref target="TRACE"/>), expose information
     2724   that was sent in request headers within the body of their response.
    27252725   Clients &SHOULD; be careful with sensitive information, like Cookies,
    27262726   Authorization credentials and other headers that might be used to
Note: See TracChangeset for help on using the changeset viewer.