<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cache on TinyChen's Blog</title><link>https://tinychen.com/tags/cache/</link><description>Recent content in Cache on TinyChen's Blog</description><generator>Hugo</generator><language>zh-cn</language><lastBuildDate>Thu, 23 Jul 2026 12:00:00 +0800</lastBuildDate><atom:link href="https://tinychen.com/tags/cache/index.xml" rel="self" type="application/rss+xml"/><item><title>Octans-媒体库图片访问与签名URL</title><link>https://tinychen.com/20260416-octans-image-access-architecture/</link><pubDate>Thu, 16 Apr 2026 12:00:00 +0800</pubDate><guid>https://tinychen.com/20260416-octans-image-access-architecture/</guid><description>&lt;p&gt;本文主要说明自托管媒体库（以 Octans 为例）在&lt;strong&gt;媒体图片访问&lt;/strong&gt;上的架构边界：谁推导 URL、谁做鉴权、HTTP 缓存与权限变更如何共处，以及 Signed URL 与「三层资产模型」相比为何更匹配家用 / 小团队私有化场景。重点是 &lt;strong&gt;CDN / 鉴权 / 缓存&lt;/strong&gt; 的分层口径，而不是接口字段或迁移 runbook。&lt;/p&gt;</description></item></channel></rss>