As I see it the directives "ProxyPassReverse" and "ProxyPassReverseCookieDomain" work almost identically, differing only in the relevant sections they change. This is also implied by the description of "ProxyPassReverseCookieDomain" (http://httpd.apache.org/docs/current/mod/mod_proxy.html#proxypassreverse): "Usage is basically similar to ProxyPassReverse, but instead of rewriting headers that are a URL, this rewrites the domain string in Set-Cookie headers."

Nevertheless, "ProxyPassReverse" accepts a balancer as argument, extracting the relevant domain information on it's own, where "ProxyPassReverseCookieDomain" does not. Actually, it does accept the balancer as argument but does not extract the relevant domain information from it, instead using it as a direct match against the "Domain" parts of cookies - which of course is not what is desired in such a use case.

I suggest to change the directives so they both use the existing code to extract the domain information from the balancer.