Custom Query (2297 matches)

Dear devs,

I think it would be nice to have "disable_header" option.

To give you an idea what I mean, I will give you an example. In my particular case I am using Piwik (open source analytics solution) which always adds "X-Frame-Options". Here is the owner's response which says that this header should be controlled by the webserver only ​https://github.com/piwik/piwik/issues/7379#issuecomment-133149429 (I believe there are more such pieces of SW that add their own extra headers)

I am okay with switching this header off in the nginx config and letting the Piwik to take the control of it, unfortunately I have the "X-Frame-Options" header set in a global config for all my vhosts (somehwere in conf.d/*.conf, my vhosts are in vhosts/*.conf) which gives me only way to split the headers among the vhost files and this is not something I want.

It would be nice to have the application-level headers control as well, and even mixed (some headers to be set by the nginx and some - by the app). Therefore I suggest to add "disable_header" flag. (or it can be named as "exclude_header" or "except_header", ...)

(an extra idea) "disable_header" could be also wildcard'ed, I bet someone would find this useful. (wildcard use case example "disable_header X-*;")

If you see my point, I would be happy to see this feature in the coming release!

I am the author of the german book: "Nginx richtig konfigurieren" (roughly translated "Configure nginx right"). As there are currently no german books on the nginx.org website it would be very much appreciated if you could add it:

<book
    title="Nginx richtig konfigurieren"
    link="https://www.amazon.de/Nginx-richtig-konfigurieren-Websites-WordPress-ebook/dp/B01GI4C982/"
    author="Oliver Gutperl"
    site="https://webserver.tips"
    publisher="Digital Sailors"
    lang="Deutsch (German)"
    cover="../books/nginx_richtig_konfigurieren.jpg" />

I'm running nginx 1.10.3 on debian stable. I have the following config:

location /http451-example/dangerous.html {
         error_page 451 /http451-example/blocked-body.html;
         add_header Link "<https://spqr.example.org/legislatione>; rel=blocked-by" always;
         return 451;
}

however, the Link header doesn't appear in the HTTP response.

Additionally, i don't see any way to provide a description associated with the numeric response code. I would normally want to see something like ​HTTP/1.1 451 Unavailable for Legal Reasons.

This can be tested with:

0 dkg@alice:~$ wget -S -O/dev/null https://dkg.fifthhorseman.net/http451-example/dangerous.html
--2017-07-15 17:17:01--  https://dkg.fifthhorseman.net/http451-example/dangerous.html
Resolving dkg.fifthhorseman.net (dkg.fifthhorseman.net)... 162.247.75.118
Connecting to dkg.fifthhorseman.net (dkg.fifthhorseman.net)|162.247.75.118|:443... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 451 
  Server: nginx/1.10.3
  Date: Sat, 15 Jul 2017 15:17:01 GMT
  Content-Type: text/html
  Content-Length: 190
  Connection: keep-alive
  ETag: "596a275f-be"
2017-07-15 17:17:02 ERROR 451: (no description).

8 dkg@alice:~$ 

​https://nginx.org/en/docs/http/ngx_http_headers_module.html#add_header says:

Adds the specified field to a response header provided that the response code equals 200, 
201, 204, 206, 301, 302, 303, 304, 307, or 308. The value can contain variables.

There could be several add_header directives. These directives are inherited from the 
previous level if and only if there are no add_header directives defined on the current 
level.

If the always parameter is specified (1.7.5), the header field will be added regardless of 
the response code.

So i think the "always" should trigger header inclusion.