I saw that ProxyPassReverseCookiePath is an Apache 2.1 directive. I fell
that perhaps it could solve some bad and obscure problems related to
cookies used by our back - end applications. Touching such applications is
too complicated. In practice they work if reverse-proxied through http and
the same relative path, they do not if reverse proxied though https or http
with another path, as I would like.
At present I am enjoying all advantages given by a debian testing
installation in the frontend - reverse-proxy machine, with an automatic
apache 2.0 configuration. So I would not like to enter complications due to
my poor knowledge of both apache and debian architectures and dependencies.
I would not like to reinstall apache 2.1 from source, with all modules and
so. In order to obtain the same result gained by
ProxyPassReverseCookiePath, do you know whether it is possible to use
directives that are 2.0 compatible ? Does a workaround exist ?
Is there a safe way in 2.0 to patch the (single ?) module developing such
What do debian users do ?
Servizi Informatici (SED)
Comune di Grosseto