Skip to content

Duplicative specification of precondition handling #665

Description

@mnot

Caching 4.3.2 re-specifies precondition processing from Semantics 13.

E.g.,

A request containing an If-None-Match header field (Section 13.1.2 of [Semantics]) indicates that the client wants to validate one or more of its own stored responses in comparison to whichever stored response is selected by the cache. If the field value is "*", or if the field value is a list of entity-tags and at least one of them matches the entity-tag of the selected stored response, a cache recipient should generate a 304 (Not Modified) response (using the metadata of the selected stored response) instead of sending that stored response.

If an If-None-Match header field is not present, a request containing an If-Modified-Since header field (Section 13.1.3 of [Semantics]) indicates that the client wants to validate one or more of its own stored responses by modification date. A cache recipient should generate a 304 (Not Modified) response (using the metadata of the selected stored response) if one of the following cases is true:

[...]

Do we want to try to fold these into Semantics so that it isn't duplicated? That would require some small adjustments to Semantics AFAICT (e.g., to make it clear what the selected representation is in each case, etc.).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions