Skip to content

IBX-11181: Added trusted_proxies ACL to Varnish setup - #65

Draft
vidarl wants to merge 2 commits into
4.6from
IBX-11181-Trusted_Proxies_is_not_set_on_Ibexa_Cloud
Draft

IBX-11181: Added trusted_proxies ACL to Varnish setup#65
vidarl wants to merge 2 commits into
4.6from
IBX-11181-Trusted_Proxies_is_not_set_on_Ibexa_Cloud

Conversation

@vidarl

@vidarl vidarl commented Aug 18, 2026

Copy link
Copy Markdown
🎫 Issue IBX-11181

Related PRs:

Description:

Supports the reverse proxy header filtering added in ibexa/http-cache#87.

varnish5/6/7.vcl now strip client supplied X-Forwarded-* and Forwarded headers unless the peer
is listed in a new trusted_proxies ACL. That ACL has to exist in parameters.vcl, since Varnish
resolves ACLs at VCL load time and otherwise refuses to load the configuration.

  • parameters.vcl gains the trusted_proxies ACL, holding localhost only. The Docker network is
    deliberately left out: nothing runs in front of Varnish in this setup, so every incoming request
    is treated as coming straight from a client.
  • entrypoint.sh gains --trusted-proxy-add, mirroring the existing --acl-add and
    --debug-acl-add flags.
  • varnish-trusted-proxy.yml is a new overlay that adds the app container to that ACL, for the
    Behat suite. It applies on top of any of varnish.yml,
    varnish7.yml or varnish9.yml, since they all define the same varnish service.

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant