4.6 Custom Headers
📘 Overview
The Custom Headers module allows you to define and inject HTTP response headers into all responses served by your ShieldsGuard-protected site. This is useful for improving security, enhancing privacy, and customizing browser behavior — without modifying your application code.
🛠️ How It Works
You define:
Header Variable Name – The name of the HTTP response header (e.g.,
X-Frame-Options
,X-Powered-By
,X-XSS-Protection
)Header Variable Content – The value of that header (e.g.,
DENY
,nosniff
, or any string)
Once created, this header will be automatically included in every HTTP response.
⚙️ How to Add a Custom Header
Navigate to Security Rules > Custom Response Headers
Click Create Header Variable
Fill in:
Header Variable Name
: the header key you want to defineHeader Variable Content
: the value you want to send
Click Create Variable
The header is now injected into all HTTP responses globally
📋 Example Use Cases
Add
X-Content-Type-Options: nosniff
to prevent MIME-type sniffingAdd
X-Frame-Options: DENY
to block clickjackingAdd
X-Powered-By: ShieldsGuard
to override default server info
🔐 Why It Matters
HTTP response headers allow you to:
Reduce browser-based attack surfaces
Hide unnecessary backend information
Enforce client-side behavior securely
This feature helps maintain a secure-by-default posture.
🎯 With just a few clicks, you can set custom headers across your entire site — no coding required.
Last updated