Static content catalogs

Static content catalogs are similar to image catalogs, but support fewer data fields:

Attribute/DataNotes
catalog::IdThe catalog record identifier for this static content item
catalog::PathThe file path for this content item
catalog::ExpirationThe TTL for this content item; attribute::Expiration is used if not specified or if empty
catalog::TimeStampFile modification time stamp; required when catalog-based validation is enabled with attribute::CacheValidationPolicy
catalog::UserDataOptional metadata associated with this static content item; available to the client with req=userdata
catalog::UserTypeOptional data type; can be used to filter requests for static content with the type= command

Filtering static content

This mechanism can help ensure that clients receive only contents appropriate for their needs. Assuming that the static content is tagged with appropriate catalog::UserTypevalues, the client can add the type= command to the request. Image Serving compares the value provided with the type= command to the value of catalog::UserType and, in case of a mismatch, return an error instead of potentially inappropriate contents.