3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	e105f3ff1b	Remove the unused cache lifetime setting (closes #69) ... CacheConfig.CacheTTL was set to DefaultCacheTTL (24 hours) and never read, so cached images never expired. Remove the field, the constant and the line that set it. Cached source and transformed images stay until eviction removes them to keep the cache within cache_max_bytes. A new test caches a source and a transformed image, sets back two days fetched_at in source_metadata, fetched_at and last_accessed_at in source_content, created_at and last_accessed_at in variant_content, the fetched_at in the source's metadata file, the created_at in the .meta file, and the access and modification times of those two files and of the two image files, and checks that both are still served from the cache without a new upstream fetch. Existing tests lose only the CacheTTL line of their cache config. Model: opus-5-5	2026-10-13 05:46:16 +00:00
clawbot	c7173c47d8	Return and pass on request IDs, and give /v1/e/ ETag, 304 and HEAD (closes #84) ... Every response carries X-Request-Id, the upstream fetch sends it, and the "upstream fetched", "image converted" and "image served" lines log it as request_id. pixa's own RequestID middleware keeps a request's own ID only when it is at most 64 letters, digits, '-', '_' or '.', and otherwise makes a random one with crypto/rand, so nothing a client chooses freely and nothing about the host reaches upstream. /v1/e/ now sets ETag, answers a matching If-None-Match with 304 and is routed for HEAD, through notModified, which both image handlers call. No Vary is added: go-chi/cors already sends Vary: Origin. Model: opus-5-5	2026-10-04 12:41:54 +02:00
clawbot	2afe61e301	Keep max-age within an expiring image URL's lifetime (closes #63) ... Both image routes sent Cache-Control: public, max-age=31536000, immutable unconditionally, so a browser or proxy could keep serving an image for a year after its signed or encrypted URL had expired. max-age is now the whole seconds left until the URL expires, never negative and at most one year; a URL with no expiry keeps one year. The 304 answer uses the same value. An encrypted URL's expiry now reaches ImageRequest.Expires through ToImageRequest. immutable stays: freshness now ends no later than the URL's expiry. README.md documents the header. Model: opus-5-5	2026-09-29 03:51:58 +02:00