[Bug 1178090] [NEW] Existing header not overwritten when using the 'always' condition with Header set

[Reed Loden]

Public bug reported:

I have an application that sets some headers, but I also have Apache
setting them as well to handle some special cases. I'm using the
mod_headers syntax of 'Header always set X-Foo "bar"'. I specifically
use the 'always' condition table, as I want to include these headers on
non-2xx responses (such as 301, 302). However, if I use 'always'
(instead of the default 'onsuccess' condition table), the headers are
duplicated, which goes against what the 'set' action is supposed to do
(overwrite any existing header).

STR:
* Have some app served by Apache set 'X-Foo: bar'
* Add 'Header always set X-Foo "bar"' to Apache config
* Notice duplicate headers
* Remove the 'always' condition, and everything will be fine (only one header)

Package: apache2 2.2.14-5ubuntu8.10
Distibution: Ubuntu 10.04.4 LTS

** Affects: apache2 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1178090

Title:
  Existing header not overwritten when using the 'always' condition with
  Header set

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1178090/+subscriptions