Doesn’t work with NGINX

  • So, the plugin documentation doesn’t do enough to communicate to a new user HOW it controls the HTTP response headers. It needs to talk about how it creates a .htaccess file for Apache web servers by default, and how it can be configured to modify a .user.ini file for PHP-FastCGI. It should also talk about how it produces configuration directives for NGINX web server, but you have to manually copy those directives into your web server’s config file or it won’t do anything.

    Since I use NGINX, this wasn’t what we wanted, because we cannot cut Devops out of the process of adding/removing HTTP Headers. We want the business to be able to simply add a header to wordpress and be done.

    I just don’t understand one thing. Why isn’t it an option to just have the HTTP Header plugin make header('{header_name}: {header_value}'); calls within PHP for each request, instead of modifying a configuration file, so that it doesn’t matter what web server you are using?

    And if it’s not possible to add the headers with PHP code, then why can’t we specify the location of the nginx.conf file for the plugin to modify, like we can for the .htaccess and .user.ini files?

Viewing 1 replies (of 1 total)
  • Plugin Author Dimitar Ivanov

    (@zinoui)

    Hey @swick4556

    Support of nginx servers is scheduled for v2, and is being developed right now.

    Using PHP to send headers is absolutety possible. Just go to Advanced settings menu and change the Default mode from Apache to PHP mode. The reason while PHP mode is not the default mode, is that it doesn’t work when caching plugins are used.

    There are plenty of tutorials across the web how to deal with .htaccess, this was never the aim of this plugin.

    It’s pity to give a low rating review without even asking for help and to complain about missing features that actually exists.

Viewing 1 replies (of 1 total)
  • The topic ‘Doesn’t work with NGINX’ is closed to new replies.