Ignore:
Timestamp:
14/05/14 16:26:01 (9 years ago)
Author:
julian.reschke@…
Message:

add status code names (#553)

File:
1 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/auth48/rfc7232.abdiff.txt

    r2674 r2675  
    209209
    210210
    211 Section 3.5., paragraph 1:
    212 OLD:
    213 
    214     The "If-Range" header field provides a special conditional request
    215     mechanism that is similar to the If-Match and If-Unmodified-Since
    216     header fields but that instructs the recipient to ignore the Range
    217     header field if the validator doesn't match, resulting in transfer of
    218     the new selected representation instead of a 412 response.  If-Range
    219     is defined in Section 3.2 of [RFC7233].
    220 
    221 NEW:
    222 
    223     The "If-Range" header field provides a special conditional request
    224     mechanism that is similar to the If-Match and If-Unmodified-Since
    225     header fields but that instructs the recipient to ignore the Range
    226     header field if the validator doesn't match, resulting in transfer of
    227     the new selected representation instead of a 412 (Precondition
    228     Failed) response.  If-Range is defined in Section 3.2 of [RFC7233].
    229 
    230 
    231211Section 4.1., paragraph 2:
    232212OLD:
    … …  
    295275
    296276
    297 Section 5., paragraph 1:
    298 OLD:
    299 
    300     Except when excluded below, a recipient cache or origin server MUST
    301     evaluate received request preconditions after it has successfully
    302     performed its normal request checks and just before it would perform
    303     the action associated with the request method.  A server MUST ignore
    304     all received preconditions if its response to the same request
    305     without those conditions would have been a status code other than a
    306     2xx or 412 (Precondition Failed).  In other words, redirects and
    307     failures take precedence over the evaluation of preconditions in
    308     conditional requests.
    309 
    310 NEW:
    311 
    312     Except when excluded below, a recipient cache or origin server MUST
    313     evaluate received request preconditions after it has successfully
    314     performed its normal request checks and just before it would perform
    315     the action associated with the request method.  A server MUST ignore
    316     all received preconditions if its response to the same request
    317     without those conditions would have been a status code other than a
    318     2xx (Successful) or 412 (Precondition Failed).  In other words,
    319     redirects and failures take precedence over the evaluation of
    320     preconditions in conditional requests.
    321 
    322 
    323277Section 7.1., paragraph 1:
    324278OLD:
Note: See TracChangeset for help on using the changeset viewer.