I would like to change all cookies to be secure and http-only. It works fine for one cookie, but doesn't work when multiple cookies are set in response.

Apache mod_header rule should change cookies from:

Set-Cookie cookie1=value; Path=/somePath
Set-Cookie cookie2=value; Path=/somePath


Set-Cookie cookie1=value; Path=/somePath; Secure; Http-Only
Set-Cookie cookie2=value; Path=/somePath; Secure; Http-Only

I use mod_headers for it with following rule:

Header edit Set-Cookie ^(.*)$ $1;Secure;HttpOnly

It works fine when only one cookie is set, but if there is more than one, it just removes all the following and they are not set at all.

Any help how to write mod_headers rule for multiple values? or the problem is in something else?

2 Answers 2


I found the answer. Problem has been in version of apache installed on server. Edit command is supported from version 2.2.4 but the version has been 2.2.3 (default on RHEL 5+). So I upgreded httpd and everything works fine.

For more about upgrading httpd on RHEL or CentOS see:




This rule would work for apache 2.2.3

Header set Set-Cookie HttpOnly;Secure
  • This doesn't seem to cause cookies to be sent with these flags, but rather just adds a value to the cookie called 'HttpOnly'...I might be wrong, but I don't think that accomplishes anything... Commented Jan 28, 2016 at 22:50
  • Never mind, I think I was mistaken. I checked the headers with this tool and it seems to have the HttpOnly setting as it should. I was confused because Chrome Developer tools and Firebug didn't seem to indicate that the cookie was HttpOnly. Commented Jan 28, 2016 at 23:02
  • I agree that something is not right here. An extra cookie is being added called "HttpOnly" - At least in Apache 2.2.12. Additionally, it breaks the application because the app doesn't expect that cookie.
    – Phaedrus
    Commented Apr 14, 2016 at 13:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .