Skip to main content

4. Defining New Cache-Status Parameters

New Cache-Status parameters can be defined by registering them in the "HTTP Cache-Status" registry.

Registration requests are reviewed and approved by a designated expert, per [RFC8126], Section 4.5. A specification document is appreciated but not required.

The expert(s) should consider the following factors when evaluating requests:

  • Community feedback

  • If the value is sufficiently well defined

  • Generic parameters are preferred over vendor-specific, application-specific, or deployment-specific values. If a generic value cannot be agreed upon in the community, the parameter's name should be correspondingly specific (e.g., with a prefix that identifies the vendor, application, or deployment).

Registration requests should use the following template:

Name: [a name for the Cache-Status parameter's key; see Section 3.1.2 of [STRUCTURED-FIELDS] for syntactic requirements]

Type: [the Structured Type of the parameter's value; see Section 3.1.2 of [STRUCTURED-FIELDS]]

Description: [a description of the parameter's semantics]

Reference: [to a specification defining this parameter, if available]

See the registry at <https://www.iana.org/assignments/http-cache-status> for details on where to send registration requests.

Last updated on