Virtual Registry 0.12.0

Released: 2026-06-11

Varnish version: 6.0.18r2

Artifact Firewall version: 0.3.1

Added

  • Added short-lived caching of GitHub GraphQL API (POST /graphql) query responses, keyed by request body. Schema introspection queries get a longer TTL, while mutations, subscriptions, and rateLimit queries bypass the cache.
  • Added preserve_host option to remotes. When enabled, the original request Host header is forwarded to the remote while the connection still targets the remote url. Useful when a single backend routes internally on the Host. Takes precedence over preserve_subdomain.
  • Added virtual_registry.base_url, a default base URL applied to all registries that do not configure their own base_url.
  • X-Forwarded-Proto: https from an upstream TLS terminator is now honored when auto-detecting the request scheme for base_url. Varnish also sets X-Forwarded-Proto toward the remote when the inbound request was TLS or when the registry’s base_url uses https://.

Changed

  • ACME challenge server no longer binds to port 80.
  • Requests that arrive with a non-canonical Host header (a bare IPv4/IPv6 literal or localhost, e.g. clients reaching a node by IP or over a local tunnel) now have their Host rewritten to the host of the applicable base_url (registry-specific or global), so they are handled as if they had arrived at the registry’s canonical hostname.

Fixed

  • Fixed config validation preventing scheme-only base_url.
  • Fixed transparent redirect-follow consuming Set-Cookie on JFrog UI and OAuth callback responses, breaking SSO login flows.

®Varnish Software, Wallingatan 12, 111 60 Stockholm, Organization nr. 556805-6203