search

httpwg / http-core

Core HTTP Specifications
https://httpwg.org/http-core/
469 stars 43 forks source link

split when to use validators into other sections #956

Closed royfielding closed 3 years ago

royfielding commented 3 years ago

Move requirements on status codes to where they will be seen. Move requirements on cache validation to where cache validation is defined. Update both for the (slightly newer) If-Range.

This is mostly editorial but rephrases some existing requirements.

fixes #933

royfielding commented 3 years ago

fixes #933

royfielding commented 3 years ago

So what we had as "client" requirements now entirely moved into the Caching spec.

Yes, because that second group of requirements are on cache validation. Hence, they are requirements on caches, not clients.

Is this because clients that are not caches really are not required to do anything with the validators?

Clients that are not caches cannot do cache validation. There are plenty of other things that clients do with validators that were not discussed by that section. The original was written by Jeff as part of the cache design document for 1.1 and thus did not include the non-cache uses of validators.

...still not sure whether not saying anything about clients in Semantics is good...

The stuff about clients is in the section on Conditional Requests (where it belongs), right? We probably should have combined them into a single section, like "Validators and Conditional Requests", but I don't want another reorg.