This Joomla Plugin implements an UI Layer for the HTTP Security headers so everyone can set and configure them from the backend.
Sponsoring and Donation
There are two ways to support me right now:
- This extension is part of Github Sponsors by sponsoring me, you help me continue my oss work for the Joomla! Project, write bug fixes, improving features and maintain my extensions.
- You just want to send me an one-time donation? Great you can do this via PayPal.me/zero24.
Thanks for your support!
This Joomla Plugin helps you to set the following HTTP Security Headers.
This plugin also comes with some easy defaults for:
Initial setup the plugin
- Download the latest version of the plugin: https://github.com/zero-24/plgsystemhttpheader/releases/latest
- Install the plugin using Upload & Install
- Enable the plugin form the plugin manager
Now the inital setup is completed and you can start configure the headers.
Please note that by default the following headers und values are set:
More Infos: https://scotthelme.co.uk/hardening-your-http-response-headers/#x-frame-options
X-XSS-Protection: 1; mode=block
More Infos: https://scotthelme.co.uk/hardening-your-http-response-headers/#x-xss-protection
More Infos: https://scotthelme.co.uk/hardening-your-http-response-headers/#x-content-type-options
More Infos: https://scotthelme.co.uk/a-new-security-header-referrer-policy/
You can allways choose to disable or change the value for one of those by changing the plugin configuration.
Force HTTP Header
Using this you can set different values from the default ones and also force headers. The supported headers are:
Here you can also decide whether the header is applyed only to the frontend and or only the backed or both sites.
HTTP Strict Transport Security (HSTS)
This option activates 'Strict Transport Security' and allows the configuration of the value of that header including
Maximum registration time (max-age) and
HSTS means that your domain can no longer be called without HTTPS. Once added to the preload list, this is not easy to undo. Domains can be removed, but it takes months for users to make a change with a browser update. This option is very important to prevent 'man-in-the-middle attacks', so it should be activated in any case, but only if you are sure that HTTPS is fully supported for the domain and all subdomains in the long run! The value for 'maximum registration time' must be set to 63072000 (2 years) for recording.
Content Security Policy (CSP)
With this option the
Content-Security-Policy rule can be set individually including an dedicated subform for the the different directives as well as setting the rules in
This plugin is translated into the following languages:
- de-DE by @zero-24
- en-GB by @zero-24 & @brianteeman
- fr-FR by @Sandra97 & @YGomiero
- it-IT by @jeckodevelopment
- nl-NL by @pe7er
You want to contribute a translation for an additional language? Feel free to create an Pull Request against the master branch.
Please note that my update server only supports the latest version running the latest version of Joomla and atleast PHP 7.0.
Any other plugin version I may have added to the download section don't get updates using the update server.
Issues / Pull Requests
You have found an Issue or have an question / suggestion regarding the plugin, or do you want to propose code changes?
Open an issue in this repo or submit a pull request with the proposed changes against the master branch.
Beyond this repo
This plugin has been included in the Joomla Core (joomla/joomla-cms#18301) and will be part of the upcomming 4.0 Release. Please note that the core the plugin has been renamed to plgsystemhttpheaders (extra
s) and extended by the new com_csp component for to core distribution.
David Jardin - @snipersister - https://www.djumla.de/ & Yves Hoppe - @yvesh - https://compojoom.com/
For giving me the inspiration for the plugin and their feedback on the actual implementation. Thanks :+1: