I'm running Apache 2.2.26:
Server version: Apache/2.2.26 (Unix)
Server built: Jan 17 2014 12:24:49
Cpanel::Easy::Apache v3.22.30 rev9999 +cloudlinux
I'm attempting to use mod_headers to edit Set-Cookie headers and add the secure or httpOnly flag, but its not working at all (Does nothing, doesn't give HTTP 500 error).
I can use the "modify" "append", directives of the Header command without an issue, just not the edit. I do not know why...
I've tried many combinations, but this is what I have in my .htaccess:
Header edit Set-Cookie "(.)([Hh][Tt][Tt][Pp][Oo][Nn][Ll][Yy])?(.)" "$1$2 ;HTTPOnly"
Header edit Set-Cookie "(.)([Ss][Ee][Cc][Uu][Rr][Ee])?(.)" "$1$2 ;Secure"
I'm open to any solution that will automatically add the flags to every Set-Cookie response, without requiring the editing of code within the application. I do not have access to install additional items on the web server, but the web server has the standard very long list of Apache modules found on most web hosts.
The Header edit directive runs before your application produces a response, so if the application is producing the header you want to edit, that header won't yet exist at the time the directive runs, and there'll be nothing for it to edit.
You can fix this by using Header always edit (which runs after your application produces a response) instead:
Header always edit Set-Cookie (.*) "$1; HTTPOnly"
An example header, before applying the directive:
Set-Cookie: foo=bar; domain=.example.com; path=/
The same header after applying the directive:
Set-Cookie: foo=bar; domain=.example.com; path=/; HTTPOnly
I'm not sure what the directives in your question are meant to do exactly; what they actually result in when changed to Header always edit (assuming the same Set-Cookie header as in my example above) is e.g.
Set-Cookie: f ;HTTPOnlyo=bar; domain=.example.com; path=/
If you understand how regexes and backreferences work, it's obvious what's happening there, but presumably it's not what you want. The directive I've given at the top of this answer ought to work for you if, as you say, you want to add the flag to every Set-Cookie header; if your needs are more complex and I've misunderstood what you're trying to do with that search/replace, let me know.
EDIT: In case it isn't obvious: to add both flags, you can either modify the directive like so:
Header always edit Set-Cookie (.*) "$1; HTTPOnly; Secure"
... or use two directives:
Header always edit Set-Cookie (.*) "$1; HTTPOnly"
Header always edit Set-Cookie (.*) "$1; Secure"
The first approach seems more sensible to me, but it's largely a matter of taste.