Changes between Initial Version and Version 1 of Ticket #479


Ignore:
Timestamp:
May 6, 2013, 9:38:45 PM (6 years ago)
Author:
mnot@…
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #479 – Description

    initial v1  
    11
    2 The If-Match condition is met if and only if any of the entity-tags
    3 listed in the If-Match field value match the entity-tag of the
    4 selected representation using the weak comparison function (as per
    5 Section 2.3.2), or if "*" is given and any current representation
    6 exists for the target resource.
     2    The If-Match condition is met if and only if any of the entity-tags
     3    listed in the If-Match field value match the entity-tag of the
     4    selected representation using the weak comparison function (as per
     5    Section 2.3.2), or if "*" is given and any current representation
     6    exists for the target resource.
    77
    88The "if and only if ... or if ..." construction looks funny. It is kind
     
    2727the level of those requirements:
    2828
    29 Preconditions are ignored if the server determines that an error or
    30 redirect response applies before they are evaluated.
     29    Preconditions are ignored if the server determines that an error or
     30    redirect response applies before they are evaluated.
    3131
    32 The conditional request header fields defined by this specification
    33 are ignored for request methods that never involve the selection or
    34 modification of a selected representation
     32    The conditional request header fields defined by this specification
     33    are ignored for request methods that never involve the selection or
     34    modification of a selected representation
    3535
    36 The general rule of conditional precedence is that exact match
    37 conditions are ...
     36    The general rule of conditional precedence is that exact match
     37    conditions are ...
    3838
    39 Specifically, the fields defined by this specification are evaluated
    40 as follows:
     39    Specifically, the fields defined by this specification are evaluated
     40    as follows:
    4141
    4242Please consider rephrasing the above using RFC 2119 keywords and, where