Overview

The Override Cache Control Headers module allows you to override the Cache-Control header at the page level. Even if your website is hosted behind a reverse proxy, you can bypass its cache by configuring the Cache-Control header for individual pages.

Key Features

Flexible Cache Control: Site administrators can override headers for multiple pages, allowing for precise control over caching behavior.
Optimized Performance: Manage each page according to specific requirements, optimizing overall site performance.
Easy Configuration: Simple and intuitive configuration through the Drupal admin interface.

Installation

Download and install the module as you would with any other Drupal module.
Enable the module from the Extend page (`/admin/modules`).

Configuration

Navigate to the module's configuration page at `/admin/config/development/override-cache-control-headers`.
Enter the URL and the desired Cache-Control headers in the provided textarea. Use the `|` symbol to separate the URL from the headers.
Example: `/sitemap.xml|must-revalidate, no-cache, private`
Enter one entry per line.

Possible Cache-Control Headers

public: Indicates that the response may be cached by any cache.
private: Indicates that the response is intended for a single user and must not be stored by shared caches.
no-cache: Forces caches to submit the request to the origin server for validation before releasing a cached copy.
no-store: The cache should not store anything about the client request or server response.
max-age=: Specifies the maximum amount of time a resource is considered fresh.
s-maxage=: Overrides max-age or the Expires header, but only for shared caches (e.g., proxies).
must-revalidate: Indicates that once a resource becomes stale, caches must not use the response without successfully validating it with the origin server.
proxy-revalidate: Similar to must-revalidate, but only for shared caches (e.g., proxies).
immutable: Indicates that the response body will not change over time.
stale-while-revalidate=: Allows a cache to serve a stale response while it revalidates it in the background.
stale-if-error=: Allows a cache to serve a stale response if the origin server returns an error.

Example Configuration

/sitemap.xml|must-revalidate, no-cache, private
/contact|no-store
/blog|public, max-age=3600

Permissions

The module provides the following permission:

Administer override cache control headers: Allows users to configure the Cache-Control headers for specific URLs.

Usage

After configuring the URLs and headers, the module will automatically apply the specified Cache-Control headers to the matching URLs. The module listens to the `kernel.response` event and modifies the response headers based on the configuration.

Technical Details

The module defines a form (`OverrideCacheControlHeadersSettingsForm`) for configuring the URLs and headers.
The event subscriber (`OverrideCacheControlHeaders`) listens to the `kernel.response` event and sets the Cache-Control headers for the specified URLs.
Configuration is stored in `override_cache_control_headers.settings.yml`.

Override Cache Control Headers

Issues

Not able to see composer require sectionActiveCode Created 14 days ago

Composer require section is not displayed ActiveCode Created 14 days ago

Not able to see composer require section
Active
Code
Created 14 days ago

Composer require section is not displayed
Active
Code
Created 14 days ago