Module Description
Overview This module allows to set HTTP response headers (both standard and non-standard) on pages by various visibility rule settings. Currently the headers can be set by path, content type and user role.

Use cases
case 1: Set 'Cache-Control' or 'Expires' header to set/reset cache behaviour of browser/cache servers. case 2: Set 'X-Frame-Options' to restrict your pages rendering on a frame. case 3: Set 'WWW-Authenticate' to set authentication to pages.

Features
* Configure list of allowed headers
* Exclude non-functional pages (e.g. Admin pages) globally
* Drush extension to cover all functionality
* Page level header rule caching
* Export/import (using Ctool) header rules from an inc file (MODULE.http_response_headers_default_rule.inc) or hook implementation (hook_http_response_headers_default_rule())

Known issues/problems
* The calculation for certain headers (e.g. Expires) happens internally and end user may not aware of it. So entering 600 in expires header value change to ISO date format of 5 minutes from current time.
* Doesn't work well with Drupal page cache

Similar projects
* Context HTTP Headers: This module allows to set header by context.

Want to help? You can help by reporting issues at the issue queue or at Github and issuing patch/pull request.

Project Usage
1638
Creation Date
Changed Date
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
This module aims to solve the problem of setting HTTP response headers on pages based on various visibility rule settings, such as path, content type, and user role.
Data Name
http_response_headers

OPENAI CHATBOT

OPENAI CHATBOT

14:35:52
Generic Chatbot
Hi, I'm a Drupal module expert powered by OpenAI, answering your questions about the Drupal module ecosystem. How can I be helpful today? Please note that we will log your question.