Expand description
Cache retrieval and deletion endpoints.
GET and DELETE /api/v1/cache/{key} take ONE key space: the request
cache_key a parse route returns (result.cache_key on POST /parse,
the cache_key in every Parquet response’s X-IFC-Metadata header). Both
resolve it through resolve_request_cache_key, so a key one of them
accepts the other accepts too, and a key one of them refuses the other
refuses with the same 400 (#5750).
Structs§
- Cache
Delete Response - Response body for
DELETE /api/v1/cache/:key. - Request
Cache 🔒Key - A request
cache_keychecked against the writer’s own key builder: the file’s sha256 plus the opening-filter and tessellation-quality suffixes, exactly ascache_key_from_partsspells them. Borrowed from the path segment it was resolved from.
Functions§
- decode_
gate 🔒 - delete_
cached - DELETE /api/v1/cache/:key - Invalidate every cache entry for the source
file a request
cache_keynames (issues #3636, #5750). - get_
cached - GET /api/v1/cache/:key - Retrieve a cached
POST /api/v1/parseresult. - not_
a_ 🔒request_ cache_ key - The rejection for a
{key}that is not a requestcache_key. Likenot_a_file_digest, the value is caller-controlled text and is not echoed. - opening_
filters 🔒 - Every opening filter a request key can carry. The
matchmakes a new variant a compile error here rather than a key both cache routes refuse. - resolve_
request_ 🔒cache_ key - THE resolver for the
{key}ofGETandDELETE /api/v1/cache/{key}. - tessellation_
qualities 🔒 - Every tessellation level a request key can carry, for the same reason.