Ignore:
Timestamp:
Jul 3, 2012, 10:25:39 AM (7 years ago)
Author:
julian.reschke@…
Message:

tune conformance requirements (see #271)

File:
1 edited

Legend:

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

    r1697 r1707  
    489489   and whether they are idempotent (<xref target="idempotent.methods"/>).
    490490   They also need to state whether they can be cached (&caching;); in
    491    particular what conditions a cache may store the response, and under what
    492    conditions such a stored response may be used to satisfy a subsequent
     491   particular under what conditions a cache can store the response, and under
     492   what conditions such a stored response can be used to satisfy a subsequent
    493493   request.
    494494</t>
     
    931931   to server &MAY; be sent immediately after the request (before a response
    932932   is received). The usual caveats also apply:
    933    data may be discarded if the eventual response is negative, and the
    934    connection may be reset with no response if more than one TCP segment
     933   data can be discarded if the eventual response is negative, and the
     934   connection can be reset with no response if more than one TCP segment
    935935   is outstanding.
    936936</t>
     
    10441044    <x:lt><t>Whether the header field is useful or allowable in trailers (see
    10451045    &chunked-encoding;).</t></x:lt>
    1046     <x:lt><t>Whether the header field should be preserved across redirects.</t></x:lt>
     1046    <x:lt><t>Whether the header field ought to be preserved across redirects.</t></x:lt>
    10471047  </list>
    10481048</t>
     
    16751675   request, a user agent &SHOULD; perform a retrieval request using the
    16761676   Location URI (a GET or HEAD request if using HTTP), which
    1677    may itself be redirected further, and present the eventual result as an
     1677   can itself be redirected further, and present the eventual result as an
    16781678   answer to the original request.
    16791679   Note that the new URI in the Location header field is not considered
Note: See TracChangeset for help on using the changeset viewer.