Opened 12 years ago

Closed 12 years ago

Last modified 11 years ago

#18 closed design (fixed)

Cache validators in 206 responses

Reported by: mnot@… Owned by:
Priority: Milestone: 01
Component: p5-range Severity:
Keywords: Cc:

Description

In Section 10.2.7 the spec implies that it may be ok to use a weak cache validator in a 206 response. The correct language is more restrictive.

If the 206 response is the result of an If-Range request that used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.

should be:

If the 206 response is the result of an If-Range request, the response SHOULD NOT include other entity-headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.

Change History (3)

comment:1 Changed 12 years ago by fielding@…

  • Milestone set to 01
  • Resolution set to fixed
  • Status changed from new to closed
  • version set to 00

Fixed in [79]

comment:2 Changed 12 years ago by mnot@…

  • version changed from 00 to d00

comment:3 Changed 11 years ago by julian.reschke@…

  • Component set to p5-range
Note: See TracTickets for help on using tickets.