Add_header works in server but not in http?

Server NGINX
1

Hello, I decided I’d clean up my configuration files for Nginx. It’s
long overdue.

I have the following in my nginx.conf but is never sent. I don’t have
another reference to this header anywhere.

add_header X-UA-Compatible
‘IE=edge,chrome=1’;

Moreover, if I move the line into a Server block, it works fine.

Docs say can be used in Http, Server and Location. I’m at a loss.

Bret

Posted at Nginx Forum:

2

Okay, then, a little more detail. In my Server block, I had an
add_header for Cache-control. When I remove that add_header, the other
one in Http appears. If I put both in Http they both appear. If I put
both in Server they both appear but it seems that the add_header removes
the headers from the parent blocks. I don’t think that was the previous
behavior.

Posted at Nginx Forum:

3

On Sat, May 14, 2011 at 11:58:26PM -0400, holstebm wrote:

Okay, then, a little more detail. In my Server block, I had an
add_header for Cache-control. When I remove that add_header, the other
one in Http appears. If I put both in Http they both appear. If I put
both in Server they both appear but it seems that the add_header removes
the headers from the parent blocks. I don’t think that was the previous
behavior.

add_header is inherited if there is no add_header on the current level.
This behavior was from from the very start.

–
Igor S.

4

I feel a little foolish. I checked the WIKI and it says “Note that it
just appends a new header entry to the output header list.” but doesn’t
say anything about the behavior you describe. I guess I hadn’t noted
this until I started moving things around so that they make more logical
sense in my config files. I had thought add_header to be cumulative
from parent to child when the headers were different (i.e. Cache-Control
in one block, X-UA-Compatible in another).

I didn’t mean to waste your time with this. I know this is a huge
project and I very much appreciate your hard work.

Posted at Nginx Forum: