Ignore:
Timestamp:
07/05/14 12:48:29 (6 years ago)
Author:
julian.reschke@…
Message:

hyphenation (#553)

File:
1 edited

Legend:

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

    r2651 r2652  
    10661066<t>
    10671067   Reactive negotiation is advantageous when the response would vary
    1068    over commonly-used dimensions (such as type, language, or encoding),
     1068   over commonly used dimensions (such as type, language, or encoding),
    10691069   when the origin server is unable to determine a user agent's
    10701070   capabilities from examining the request, and generally when public
     
    11951195   This definition of safe methods does not prevent an implementation from
    11961196   including behavior that is potentially harmful, not entirely read-only,
    1197    or which causes side-effects while invoking a safe method.  What is
     1197   or which causes side effects while invoking a safe method.  What is
    11981198   important, however, is that the client did not request that additional
    11991199   behavior and cannot be held accountable for it.  For example,
     
    12021202   considered safe even though the log storage might become full and crash
    12031203   the server.  Likewise, a safe request initiated by selecting an
    1204    advertisement on the Web will often have the side-effect of charging an
     1204   advertisement on the Web will often have the side effect of charging an
    12051205   advertising account.
    12061206</t>
     
    12321232   the resource owner &MUST; disable or disallow that action when it is
    12331233   accessed using a safe request method. Failure to do so will result in
    1234    unfortunate side-effects when automated processes perform a GET on
     1234   unfortunate side effects when automated processes perform a GET on
    12351235   every URI reference for the sake of link maintenance, pre-fetching,
    12361236   building a search index, etc.
     
    12521252   what has been requested by the user; a server is free to log each request
    12531253   separately, retain a revision control history, or implement other
    1254    non-idempotent side-effects for each idempotent request.
     1254   non-idempotent side effects for each idempotent request.
    12551255</t>
    12561256<t>
     
    15221522</t>
    15231523<t>
    1524    A PUT request applied to the target resource can have side-effects
     1524   A PUT request applied to the target resource can have side effects
    15251525   on other resources.  For example, an article might have a URI for
    15261526   identifying "the current version" (a resource) that is separate
     
    25252525<t>
    25262526   Some intermediaries have been known to indiscriminately remove Referer
    2527    header fields from outgoing requests. This has the unfortunate side-effect
     2527   header fields from outgoing requests. This has the unfortunate side effect
    25282528   of interfering with protection against CSRF attacks, which can be far
    25292529   more harmful to their users. Intermediaries and user agent extensions that
     
    25682568   A sender &SHOULD; limit generated product identifiers to what is necessary
    25692569   to identify the product; a sender &MUST-NOT; generate advertising or other
    2570    non-essential information within the product identifier.
     2570   nonessential information within the product identifier.
    25712571   A sender &SHOULD-NOT; generate information in <x:ref>product-version</x:ref>
    25722572   that is not a version identifier (i.e., successive versions of the same
     
    28772877</t>
    28782878<t>
    2879    The 202 response is intentionally non-committal. Its purpose is to
     2879   The 202 response is intentionally noncommittal. Its purpose is to
    28802880   allow a server to accept a request for some other process (perhaps a
    28812881   batch-oriented process that is only run once per day) without
Note: See TracChangeset for help on using the changeset viewer.