The purge module clears URLs from reverse proxy caches like Varnish, Squid or Nginx by issuing an http PURGE request to them. It works in conjunction with the Cache Expiration module to act on events that are likely to expire URLs from the proxy cache and interact with Rules and Drush. This allows delivering content updates faster to end users.



  • Unpack, place and enable just like any other module.
  • Navigate to Administration -> Site configuration -> Purge settings
  • Set your proxy URL(s) like http://localhost or
  • If you are using nginx you need to specify the purge path and the get method in
    your proxy setting like this:
  • If you are using the Acquia Dev Cloud or the Acquia Managed Hosting servcies you'll need to configure like: I recommend you use the platform specific module Acquia Purge instead to overcome limitations in Acquia Purge 1.x. These will be addressed in a sustainable way in the upcoming 2.x branch of Purge.
  • Optional: Install Rules for advanced cache clearing scenarios or Drush for command line purging. Both are supported through the expire module.


The 1.x versions of Drupal 6 and Drupal 7 will not longer receive new features, just bugfixes and are believed to be stable.
The 7.x-2.x branch will be the place where new features will be developed. The Drupal 6 branch may receive backports of some new features but most likely not all of them, depending on demand and community involvement. Some of the new 2.x features we're thinking about:

  • New configuration interface
  • Proxy settings auto discovery
  • Dropping hard dependency on Expire and Curl library
  • More request handlers besides concurrent curl requests.
  • Wildcard purge url's including purging of whole domains.
  • Your feature here

See #1826926: Purge 2.x roadmap and progress for more details and status updates.

Project Information