Crawler Rate Limit allows you to limit requests performed by web crawlers, bots, and spiders. It can also rate limit regular traffic, and block requests based on autonomous system number (ASN). It limits number of requests crawler/visitor is allowed to perform in the given time interval. After the limit is exceeded server will respond with HTTP code 429 (Too many requests).
The Cloudflare Purge module provides an easy and secure way to manually purge Cloudflare cache from within your Drupal site. It uses the Guzzle HTTP client instead of raw cURL and supports both API Key and Bearer Token authentication methods.
This module replicates the functionality of the following cURL command using Drupal’s internal HTTP API:
It also allows purging specific URLs from the Cloudflare cache via a dedicated form, offering finer cache control for developers and editors.
Features
Supports both API Key and Bearer Token authentication.
Allows purging all cache or individual URLs.
Provides a secure, permissions-based interface for cache purging.
Credentials can be configured via the admin UI or settings.php.
Typical Use Cases
Your hosting provider enables Cloudflare but doesn’t support Drupal-based purging.
You’re using the Cloudflare module but can’t install its purge submodule.
You need a lightweight alternative for targeted cache control in development or production.
Security
All requests are routed through Drupal's Guzzle HTTP client with CSRF protection and proper permissions, ensuring safe integration without exposing sensitive data.
This module enables any Drupal user with permissions to manually clear Acquia Cloud varnish cache for each environment. It employs the Acquia Cloud API V2 as suggested by Acquia.
Is Acquia Purge Varnish Secure?
It incorporates a custom CSRF token in Drupal and utilizes the Guzzle HTTP client for all API calls. Hence, it's not susceptible to CSRF exploits and mitigates security risks.