On Sat, Feb 4, 2017 at 4:56 PM, wrote:
> We recently upgraded to Apache 2.2.32 and are facing issues with F5 health
> check. The openssl s_client from F5 to check Apache web server’s health is
> being returned by the 2.2.32 server as 400 error. We don’t see the issue
> with 2.2.31 however. The ap
Hi!
2017-02-04 22:56 GMT+01:00 :
> Hi,
>
> We recently upgraded to Apache 2.2.32 and are facing issues with F5 health
> check. The openssl s_client from F5 to check Apache web server’s health is
> being returned by the 2.2.32 server as 400 error. We don’t see the issue
> with 2.2.31 however. The
Hi,
We recently upgraded to Apache 2.2.32 and are facing issues with F5 health
check. The openssl s_client from F5 to check Apache web server's health is
being returned by the 2.2.32 server as 400 error. We don't see the issue with
2.2.31 however. The application can be accessed with web server
On 04/02/2017 07:40, Eric Covener wrote:
Internal redirects, which happen for almost any substitution in
htaccess rewritees, cause existing environment variables to be renamed
to REDIRECT_$varname.
Thanks Eric.
-
To unsubscrib
On Sat, Feb 4, 2017 at 2:03 AM, Nigel Peck wrote:
> What is going on? Am I missing something? Surely an environment variable
> should not disappear again on the next iteration.
Internal redirects, which happen for almost any substitution in
htaccess rewritees, cause existing environment variable
