You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next are the common security headers being set. It's worth noting that special value of `omit` for directives below
78
-
will disable sending a particular header by the module (useful if you want to let your backend app to send it).
78
+
It's worth noting that some of those headers bear functional use, e.g. [`X-Page-Speed` docs](https://www.modpagespeed.com/doc/configuration#XHeaderValue) mention:
79
+
80
+
> ... it is used to prevent infinite loops and unnecessary rewrites when PageSpeed
81
+
> fetches resources from an origin that also uses PageSpeed
82
+
83
+
So it's best to specify `hide_server_tokens on;` in a front-facing NGINX insances, e.g.
84
+
the one being accessed by actual browsers, and not the ones consumed by Varnish or other software.
85
+
86
+
In most cases you will be just fine with `security_headers on;` and `hide_server_tokens on;`, without any adjustments.
87
+
88
+
For fine-tuning, use the header-specific directives below.
89
+
A special value `omit` disables sending a particular header by the module (useful if you want to let your backend app to send it).
79
90
80
91
### `security_headers_xss`
81
92
@@ -141,6 +152,7 @@ To compile the module into NGINX, run:
141
152
make
142
153
make install
143
154
144
-
Or you can compile it as dynamic module. In that case, use `--add-dynamic-module` instead, and load the module after compilation via:
155
+
Or you can compile it as dynamic module. In that case, use `--add-dynamic-module` instead, and load the module after
0 commit comments