Is reverse proxy different from hosting-side page caching in hosting?

  • Resolved sinorgpl

    (@sinorgpl)


    3 years, 10 months ago

    Hello,

    I am looking into enabling reverse proxy via w3tc. I see that w3tc asks for Varnish IP, however my hosting provider recently replaced Varnish with another, “better Varnish” custom caching system, enabled in their web panel in page settings without any IP configuration. My questions is should I just ran varnish via ssh and use that for reverse proxy, is it any different from using the caching system offered by my hosting provider? I am not sure how is hosting-side page caching different from Varnish reverse proxy.

    thank you for any advise

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Jesse Owens

    (@jessecowens)

    Hi @sinorgpl

    Generally speaking, unless you’re very familiar with setting up and configuring Varnish or you’re using multiple varnish servers for scaling up to very high traffic, your hosting provider’s option is likely much easier to use.

    It’s likely that your host is using an NGINX reverse-proxy cache, which has much better support for TLS/SSL websites.

    Thread Starter sinorgpl

    (@sinorgpl)

    Thank you for your answer. I have a small webshop.

    So just to be clear, it should be fine to enable the hosting-side caching on top of all my CDN / caching settings in w3tc? Of course unless I notice any issues.

    Plugin Support Jesse Owens

    (@jessecowens)

    Hi @sinorgpl

    I couldn’t say for sure, but if you do use it you may need to flush the hosting cache manually when you purge your caches, depending on how your host has it configured.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Is reverse proxy different from hosting-side page caching in hosting?’ is closed to new replies.