<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Artifact Firewall Changelog on Varnish Orca</title><link>/orca/docs/firewall-changelog/</link><description>Recent content in Artifact Firewall Changelog on Varnish Orca</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Sat, 13 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="/orca/docs/firewall-changelog/index.xml" rel="self" type="application/rss+xml"/><item><title>Artifact Firewall 0.3.2</title><link>/orca/docs/firewall-changelog/0.3.2/</link><pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate><guid>/orca/docs/firewall-changelog/0.3.2/</guid><description>Released: 2026-06-13
Fixed Manifests and artifacts served through a JFrog Artifactory virtual repo are now correctly identified, filtered, and rewritten — in both standalone and integrated mode, with no configuration. Previously the package path was assumed to sit at the registry root, so these requests were skipped (&amp;ldquo;not a transform path&amp;rdquo;). npm / PyPI: the Artifactory API prefix (.../api/&amp;lt;type&amp;gt;/&amp;lt;repo&amp;gt;/) is stripped before identification. Maven: maven-metadata.xml and .pom files are evaluated against the coordinates in the document body, not the URL path.</description></item><item><title>Varnish Artifact Firewall 0.3.1</title><link>/orca/docs/firewall-changelog/0.3.1/</link><pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate><guid>/orca/docs/firewall-changelog/0.3.1/</guid><description>Released: 2026-06-03
Fixed Fixed rule engine initialization issue when only git fetchers are used. Issue was introduced in 0.3.0.</description></item><item><title>Varnish Artifact Firewall 0.3.0</title><link>/orca/docs/firewall-changelog/0.3.0/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>/orca/docs/firewall-changelog/0.3.0/</guid><description>Released: 2026-06-02
Added Standalone deployment mode, now the default. The firewall sits directly in front of one or more origin registries and routes requests itself. Automatic detection of registry from the Accept header, User-Agent prefix, and URL path pattern. Requests that can&amp;rsquo;t be classified stream through unchanged. Per-version artifact preflight: direct downloads of tarballs (npm .tgz), wheels/sdists (PyPI), and .nupkg files are blocked at 403 when a per-version deny rule applies, preventing bypass via hard-coded artifact URLs.</description></item><item><title>Varnish Artifact Firewall 0.2.2</title><link>/orca/docs/firewall-changelog/0.2.2/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>/orca/docs/firewall-changelog/0.2.2/</guid><description>Released: 2026-05-11
Added Added support for the NuGet ecosystem Added a mode option to the Artifact Firewall configuration, which can change the behavior of the firewall. Includes normal (default), hide and report. Changed Audit log now includes an effective_action field, which for modes other than normal can be different than the action field. Changed log level for some chatty package quarantine logs to debug.</description></item><item><title>Varnish Artifact Firewall 0.1.1</title><link>/orca/docs/firewall-changelog/0.1.1/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>/orca/docs/firewall-changelog/0.1.1/</guid><description>Released: 2026-04-21
Added Initial release.</description></item></channel></rss>