https://bz.apache.org/bugzilla/show_bug.cgi?id=62380
Bug ID: 62380
Summary: Existing header not overwritten when using the
'always' condition with Header set
Product: Apache httpd-2
Version: 2.4.29
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_headers
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Hi, I'm reporting a bug that is already well described here
(https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1178090):
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 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).
I'm confirm that this bug affect the more recent Apache 2.4.29, compiled from
the official source distribution on Linux RHEL 7.4
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
