Inconsistent Varnish Detection

  • Gulshan Kumar

    (@thegulshankumar)


    1 week, 2 days ago

    Generally, this plugin works very well. However, I noticed an inconsistency in the Varnish detection.Error Message

    Please make sure that your server has Varnish Cache

    When It Occurs

    The issue occurs when Cloudflare is active and I enter only:

    127.0.0.1

    The plugin reports that Varnish is not detected. While same address without Port is accepted when CF proxy isn’t active.

    Current Workaround for Cloudflare

    It works correctly when I manually append the default Varnish port:

    127.0.0.1:6081

    Expected Behavior

    Ideally, the port should always be required for the Varnish server address, since the detection depends on the correct port.

    A better UX would be to prefill the port with the default Varnish port (6081) in case of Cloudflare/Without Cloudflare, so the field initially contains:

    127.0.0.1:6081

    The user could then change the port if their Varnish configuration uses a different one.

    This would also prevent the detection from failing simply because the port was omitted.

    Thank you.

Viewing 1 replies (of 1 total)
  • Plugin Author Emre Vona

    (@emrevona)

    1 week, 2 days ago

    Thank you so much.

    What you said is very true in this example, but generally, Varnish cache doesn’t require port information. You’ve found a very good solution.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.