ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
The goal is to prevent duplicate writes when Nginx retries an upstream request while a stale response is being served via proxy_cache_use_stale. Nginx documentation does not define how proxy_next_upstream retry settings interact with proxy_cache_use_stale, leaving uncertainty about whether retries will bypass the cache or trigger new upstream calls for unsaf
Problem Context When an upstream registry updates a mutable tag, Harbor’s proxy cache may still serve a previously cached manifest. The Docker client then receives a 404 Not Found when pulling the new digest, indicating that the proxy cache has not yet been refreshed. Constraints & Uncertainty Proxy cache entries are governed by a configurable TTL, and H
Goal is to understand cache freshness and credential isolation when using the project-scoped proxy cache instead of the legacy per-registry pull-through cache. The feature binds upstream registry credentials to a dedicated proxy-cache project rather than using global configuration, which changes multi-tenant isolation. Cached manifests and blobs are served f
harbor
nginx