I had a file 'apache.conf'' which ran fine under Apache 2.2. But on some
machines we now find Apache 2.4 and it is not upward compatible.
Note that MS-DOS 1.0 will still run on a brand new Intel chip: that's
upward compatibility.
Today I have two config files, apache2.2.conf and apache2.4.conf.
Then why did you upgraded w/o testing?
The docs say things changed and you should change the config files to use.
You can still downgrade too.
On Wed, May 21, 2014 at 5:44 AM, Andy Canfield andycanfi...@yandex.comwrote:
I had a file 'apache.conf'' which ran fine under Apache 2.2. But on some
I'm getting an odd error with a slightly edge Apache Subject Name
Identifier (SNI) configuration: the SSL negotiation concludes correctly,
but I get a 403 error, as if I was using a non-SNI compatible browser
when I access an SNI domain with a subjectAltName (SAN) cert
On Sat, May 17, 2014 at 4:37 AM, Andy Canfield andycanfi...@yandex.com wrote:
Last week, if you went to http://www.andycanfield.com, you would see my web
site. Today, if you go there, you will see Internal Server Error. Apache
broke it.
We had four sites on that computer:
[1]
Dear all
i know that is possible to use a route parameter into the proxy balancer
definition and then set a stickysession cookie name into the ProxyPass
setting.
Example:
ProxyPass / balancer://mycluster/ stickysession=MyCookie
ProxyPassReverse / balancer://mycluster/
