The add_header with always in NGINX allows us to add a custom header to the server’s response. Bobcares, as a part of our Server Management Service offers solutions to every query that comes our way.

The add_header with always in NGINX

In NGINX, the add_header command with the always option allows us to include a custom header in the server’s response despite of the HTTP status code. By default, the add_header directive only includes the provided header in responses with specific HTTP status codes. These often include both successful responses (200, 201, 301, etc.) and error responses (404, 500, etc.).

The always overrides the default behavior. If we want to ensure a header is added regardless of whether it’s already present or not, we can use the always parameter with the add_header directive. When we use include always with the add_header directive, the specified header is added to all responses, regardless of status code.

How to Use it?

Several scenarios may need the constant use of add_header:

Security Headers: Certain security headers, such as X-Frame-Options or Strict-Transport-Security (HSTS), must be applied to all responses to make sure that security protections are consistent throughout the website.

Caching Headers: We may want to specify caching behavior for all resources on the server, regardless of status code. For example, specifying Cache-Control: no-cache prevents clients from caching any answers.

CORS Setup: If we are using CORS on the Nginx server, we may need to include CORS headers in all responses to allow access from particular origins.

An Example

So, the provided NGINX settings ensures that all responses from the server include the X-Frame-Options header with a value of “SAMEORIGIN” and the Cache-Control header with a value of “no-cache”.

[Need to know more? Get in touch with us if you have any further inquiries.]

Conclusion

This post explains about the use of add_header with always option on NGINX from our Tech team.