Re: mod_headers bug?

["Neil Simons" <neilsimonsglint@xxxxxxxxxxx>]

[ mod_headers cannot modify existing headers ]

 

In case anyone comes across the same problem, I have not found a solution.

I have run the simple tests below on a xampp-dsl virtual machine, and they work exactly as I expect they should, leading me to believe that there is something fundamentaly wrong with httpd 2.2.2 installed on fedora core 5.

 

I will simply be scrapping fc5 and installing f7, hoping that this is a bug exclusive to httpd v 2.2.2 / fc5.

 

 

----- Original Message -----

From: Neil Simons

To: users@xxxxxxxxxxxxxxxx

Sent: Monday, April 07, 2008 5:51 PM

Subject: mod_headers bug?

Has anyone had experiences where mod_headers directives often fail to have any effect?

- It is unable to modify headers, only create & modify newly added headers.

 

Within my .htaccess file I carried out the following simple tests.

 

1)

Header always set MyCustomHeader myCustomValue

-- this works fine

 

Header always set MyCustomHeader2 unsetMe

Header always unset MycustomHeader2

-- works as expected - the header is not in the response

 

2)

Header always set Cache-Control max-age=33

-- this works ONLY if apache doesnt normally include a Cach-Control header of its own accord.

 

3)

Header always set Cache-Control max-age=33

Header always unset Cache-Control

-- as with 2), this works ONLY if apache hasnt already added such a header

 

 

It seems that mod_headers cannot operate on *existing* headers! - Only on headers generated by itself!

I have searched through various bug lists, archives, documentation etc.. but to no avail.

 

NB, I have used the 'always' condition keyword to ensure all header tables are used. Without this keyword, the tet results are the same.

 

 

Environment:

Linux, Fedora Core 5

httpd 2.2.2

 

 

Regards,

Neil Simons