Ignore:
Timestamp:
14/05/14 12:57:45 (7 years ago)
Author:
julian.reschke@…
Message:

grammar (#553)

File:
1 edited

Legend:

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

    r2669 r2670  
    77 Obsoletes: 2616 (if approved)                            J. Reschke, Ed.
    88 Intended status: Standards Track                              greenbytes
    9  Expires: November 14, 2014                                  May 13, 2014
     9 Expires: November 15, 2014                                  May 14, 2014
    1010
    1111NEW:
     
    8888    time.  It is inappropriate to use Internet-Drafts as reference
    8989    material or to cite them other than as "work in progress."
    90     This Internet-Draft will expire on November 14, 2014.
     90    This Internet-Draft will expire on November 15, 2014.
    9191
    9292NEW:
     
    139139    value when it is necessary to invalidate the stored responses held by
    140140    remote caches and authoring tools.
    141 
    142 
    143 Section 2.1., paragraph 6:
    144 OLD:
    145 
    146     In contrast, a "weak validator" is representation metadata that might
    147     not change for every change to the representation data.  This
    148     weakness might be due to limitations in how the value is calculated,
    149     such as clock resolution or an inability to ensure uniqueness for all
    150     possible representations of the resource, or due to a desire by the
    151     resource owner to group representations by some self-determined set
    152     of equivalency rather than unique sequences of data.  An origin
    153     server SHOULD change a weak entity-tag whenever it considers prior
    154     representations to be unacceptable as a substitute for the current
    155     representation.  In other words, a weak entity-tag ought to change
    156     whenever the origin server wants caches to invalidate old responses.
    157 
    158 NEW:
    159 
    160     In contrast, a "weak validator" is representation metadata that might
    161     not change for every change to the representation data.  This
    162     weakness might be due to limitations in how the value is calculated,
    163     such as clock resolution, an inability to ensure uniqueness for all
    164     possible representations of the resource, or a desire of the resource
    165     owner to group representations by some self-determined set of
    166     equivalency rather than unique sequences of data.  An origin server
    167     SHOULD change a weak entity-tag whenever it considers prior
    168     representations to be unacceptable as a substitute for the current
    169     representation.  In other words, a weak entity-tag ought to change
    170     whenever the origin server wants caches to invalidate old responses.
    171141
    172142
     
    351321
    352322
    353 Section 5., paragraph 2:
    354 OLD:
    355 
    356     A server that is not the origin server for the target resource and
    357     cannot act as a cache for requests on the target resource MUST NOT
    358     evaluate the conditional request header fields defined by this
    359     specification, and MUST forward them if the request is forwarded,
    360     since the generating client intends that they be evaluated by a
    361     server that can provide a current representation.  Likewise, a server
    362     MUST ignore the conditional request header fields defined by this
    363     specification when received with a request method that does not
    364     involve the selection or modification of a selected representation,
    365     such as CONNECT, OPTIONS, or TRACE.
    366 
    367 NEW:
    368 
    369     A server that is not the origin server for the target resource and
    370     cannot act as a cache for requests on the target resource MUST NOT
    371     evaluate the conditional request header fields defined by this
    372     specification, and it MUST forward them if the request is forwarded,
    373     since the generating client intends that they be evaluated by a
    374     server that can provide a current representation.  Likewise, a server
    375     MUST ignore the conditional request header fields defined by this
    376     specification when received with a request method that does not
    377     involve the selection or modification of a selected representation,
    378     such as CONNECT, OPTIONS, or TRACE.
    379 
    380 
    381323Section 7.1., paragraph 1:
    382324OLD:
Note: See TracChangeset for help on using the changeset viewer.