Add additional reverse proxy alternative for Zero Config Purger

Created on 6 April 2022, about 2 years ago
Updated 2 April 2024, 3 months ago

Problem/Motivation

We have a situation in a more complex environment that our reverse proxy will pass something different than the varnish proxy that we need to call to flush it.
Another issue is also that you need an ip address, and a hostname will not be valid.

Proposed resolution

- Add varnish_purge_zeroconfig_host settings variable as another way to define reversed proxies.
- remove the check (strpos('.')) on the reverse proxy addresses.

✨ Feature request
Status

Needs review

Version

2.0

Component

Code

Created by

πŸ‡³πŸ‡±Netherlands jefuri

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States dasginganinja Bethlehem, PA

    I'm running into this issue as I'm looking to get off of the Bundled purger.

    We've tried to do some unwinding of our $settings['reverse_proxy_addresses'] but have ran into the issues described above.

    Is there some sort of way that this "zero config" purger (which appears to be the best out of the bunch due to supporting many invalidation types) can have a settings form or at least be more configurable from a code approach?

    I could see the main functionality of the purger coming into another base of sorts and have different methods of instantiation.
    For example, if somebody wanted to use the zero config functionality that would be possible, but there could also be a settings form for configuring the instance.

    I've looked into potentially using PHP Reflection classes to override some site settings in the object to make it work with this functionality but I'd hate to have to maintain something custom on my end that the community would benefit from.

Production build 0.69.0 2024