GD Security Headers
Configure various security related HTTP headers, including Content Security Policy, Referrer Policy and more. All headers can be added to .HTACCESS file.
Supports
Most Helpful Content for GD Security Headers
Can I translate plugin to my language?
Yes. POT file is provided as a base for translation in the root folder for each plugin. Translation files should go into languages directory, and WordPress must be set to your language to load the file. As an alternative, translation file can go into wp-content/languages/plugins directory.
The file name for translated and compiled MO file must be the same as POT file with the addition of language code: {plugin-name}-{language-code}.mo.
You can check out this for translating plugins using POEdit program:
support.dev4press.com/kb/article/translating-plugins-or-themes-using-poedit
How can I translate plugin to my language?
All Dev4Press free and lite plugins can be translated via WordPress.org and their translation services. Each plugin on WordPress.org has support for translation, and you can get to it through the plugin Developer panel. To translate plugins on WordPress.org, you need a WordPress.org account. But, if you want to handle translations on your own, each plugin has a POT file with the list of all translation strings
Does plugin works with WordPress MultiSite installations?
Yes. Plugin must be activated as Network Wide.