The error message “add_header directive is not allowed here” usually appears when we try to use the add_header directive in a web server config file (such as Nginx) when it is not allowed. Bobcares, as a part of our Server Management Service offers solutions to every query that comes our way.

Solving “add_header directive is not allowed here”

The Nginx config file is split up into multiple contexts, each with a distinct function. Location, server, http, and main are the primary contexts. Every Nginx directive has a specific context in which it can be used. So, an error occurs if a directive is placed outside of its intended context.

In order to append HTTP headers to a response, we can use the add_header directive. Setting custom headers for caching, security, or client details can all benefit from this. The add_header directive isn’t permitted in all situations, though. It is typically used in the contexts of servers, locations, as well as http. Let’s see how we can use the add_header directive within a server block

In this example, the X-Content-Type-Options header is added to responses for requests matching the root location by using the add_header directive inside a location block.

Quick Fixes

1. It’s time to fix the Nginx setup when we see the error message “emerg add_header directive is not allowed here.” Examining the context in which we’ve placed the add_header directive is the first step. Make sure it’s contained in a location, server, or http block.

2. Another issue is misplacing the add_header directive directly within the main context or within an unsupported block. So, to fix this, we must move the add_header directive into a server or location block.

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

Conclusion

The article offers a brief note on “add_header directive is not allowed here” troubleshooting.