Proxy Cache Purge

Hospedagem WordPress com plugin Proxy Cache Purge

Onde hospedar o plugin Proxy Cache Purge?

Este plugin pode ser hospedado em qualquer servidor que possua WordPress instalado. Recomendamos optar por uma empresa de hospedagem de confiança, com servidores otimizados para WordPress, como o serviço de hospedagem WordPress da MCO2.

Hospedando o plugin Proxy Cache Purge em uma empresa de hospedagem seguro

A MCO2, além de instalar o WordPress na versão mais atual para seus clientes, fornece o WP SafePress, um sistema singular que salvaguarda e melhora seu site simultaneamente.

Por que a Hospedagem WordPress funciona melhor na MCO2?

A Hospedagem WordPress funciona melhor pois a MCO2 possui servidores otimizados para WordPress. A instalação de WordPress é diferente de uma instalação trivial, pois habilita imediatamente recursos como otimização automática de imagens, proteção da página de login, bloqueio de atividades maliciosas diretamente no firewall, cache avançado e HTTPS ativado por padrão. São plugins que potencializam seu WordPress para a máxima segurança e o máximo desempenho.

This plugin does not install nor configure a cache proxy. It acts as an interface with such services.

One common method of caching content for websites is via the use of reverse proxy caching. Common examples of this are Varnish and Nginx. These systems allow a website to update content and have the visitor’s experience cached without the need for complex plugins storing the files locally and using up a user’s disk space.

A reverse proxy cache is installed in front of a server and reviews requests. If the page being requested is already cached, it delivers the cached content. Otherwise it generates the page and the cache on demand.

The Proxy Cache Purge plugin sends a request to delete (aka flush) the cached data of a page or post every time it’s modified.

How It Works

When content on a site is updated by WordPress, the plugin reaches out to the proxy cache service with the URL of the page, requesting the cache be deleted.

Not all page are deleted from the cache on every change. For example, when a post, page, or custom post type is edited, or a new comment is added, only the following pages will purge:

• The front page
• The post/page edited
• Any categories, tags, and/or custom taxonomies associated with the page
• Related feeds
• Associated JSON API pages

In addition, your entire cache will be deleted on the following actions:

• Changing themes
• Pressing the Empty Cache button on the toolbar

Plugins can hook into the purge actions as well, to filter their own events to trigger a purge.

On a multisite network using subfolders, only network admins can purge the main site.

Development Mode

If you’re working on a site and need to turn off caching in one of two ways:

1. Add define( 'VHP_DEVMODE', true ); to your wp-config.php file
2. Go to Proxy Cache -> Settings and enable debug mode for 24 hours at a time

That will break cache on page loads. It is not recommended for production!

WP CLI

Purge

Purge commands let you empty the cache.

• wp varnish purge – Flush the cache for your front page
• wp varnish purge [<url>] – Flush the cache for one URL

You can use the parameter --wildcard to empty everything from that URL down. So if you wanted to empty cache for all themes, you would do this:

• wp varnish purge https://example.com/wp-content/themes --wildcard

Debug

Debugging can help you figure out why your cache isn’t working as well as it could. The default is for your home page, but you can pass any URL on your domain.

• wp varnish debug [<url>]

Available parameters:

• [--include-headers] — Include headers in debug check output
• [--include-grep] — Grep active theme and plugin directories for common issues

DevMode

Development mode allows you to disable the cache, temporarily.

• wp varnish devmode [<activate|deactivate|toggle>] – Change development mode state

Privacy Policy

As of version 5, this plugin no longer uses any remote data.