Adam Andrzej Jaworski authored Nov 08, 2016 and Adam Andrzej Jaworski committed Nov 08, 2016

Issue #2825254 by memtkmcc: Debian upgrade - Nginx - invalid number of arguments in "add_header" directive

Grazyna Jaworska authored Jul 18, 2016 and Adam Andrzej Jaworski committed Oct 21, 2016

# Conflicts:
#	http/Provision/Config/Nginx/subdir.tpl.php

Grazyna Jaworska authored Aug 24, 2016 and Adam Andrzej Jaworski committed Oct 21, 2016

This should be set in /data/conf/global.inc with optional OFF switch in the platform and site level INI files.

Grazyna Jaworska authored Jul 23, 2016 and Adam Andrzej Jaworski committed Oct 21, 2016

“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.” — http://nginx.org/en/docs/http/ngx_http_headers_module.html

# Conflicts:
#	http/Provision/Config/Nginx/subdir.tpl.php

Issue #2731605 by gboudrias - Hardcoded hosting_le code limits behavior with regards to the .well-known directory

This prevents caching/sharing errors and 403 responses for all anonymous visitors when custom fastcgi_cache_valid is forced via header('X-Accel-Expires: 300'); etc.

Issue #2685575 by NWOM -- Nginx: whitelist xmlrpc.php when /etc/nginx/basic_nginx.conf ctrl file is present

More details at: https://www.drupal.org/node/2599326

It is important to use $request_uri, because it allows you to send HTTPS redirect with original URI (and $args, if you skip "?"), while $uri can be potentially modified, even theoretically, because it is $request_uri after internal rewrites, if present in the configuration.

This header will be sent only for already generated derivatives, which are effectively static files. For not yet generated derivatives, the request is sent to @DruPal backend and thus any extra headers specified in the location are ignored.