@httpd] Apache 2.2.32 failing F5 health check
On Mon, Feb 6, 2017 at 8:40 PM, wrote:
> broken apache httpd version 2.2.32:
>
> openssl s_client -connect : -pause
>
> when paused input this.
>
> GET /login/healthcheck/content_check.wecv HTTP/1.0
>
> Host:
s_client doesn&
On Mon, Feb 6, 2017 at 8:40 PM, wrote:
> broken apache httpd version 2.2.32:
>
> openssl s_client -connect : -pause
>
> when paused input this.
>
> GET /login/healthcheck/content_check.wecv HTTP/1.0
>
> Host:
s_client doesn't send CRLF unless you pass -crlf.
---
2017 5:00 PM
To: users@httpd.apache.org<mailto:users@httpd.apache.org>
Subject: Re: [users@httpd] Apache 2.2.32 failing F5 health check
On Sat, Feb 4, 2017 at 4:56 PM,
mailto:bharath.c.ko...@wellsfargo.com.invalid>>
wrote:
> We recently upgraded to Apache 2.2.32 and are facing issues with F5
n the configuration, but when we upgrade
> to 2.2.32, apache reports a 400 error.
>
> Bharath Kolla
>
>
>
> -Original Message-
> From: Eric Covener [mailto:cove...@gmail.com]
> Sent: Saturday, February 04, 2017 5:00 PM
> To: users@httpd.apache.org
> Subjec
-
From: Eric Covener [mailto:cove...@gmail.com]
Sent: Saturday, February 04, 2017 5:00 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Apache 2.2.32 failing F5 health check
On Sat, Feb 4, 2017 at 4:56 PM, wrote:
> We recently upgraded to Apache 2.2.32 and are facing issues with
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
