You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Bh...@wellsfargo.com.INVALID on 2017/02/04 21:56:30 UTC

[users@httpd] Apache 2.2.32 failing F5 health check

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 listen address, but when accessed through the VIP, it sends a 400. Any help in debugging this issue will be much appreciated.

Thanks,

Bharath

RE: [users@httpd] Apache 2.2.32 failing F5 health check

Posted by Bh...@wellsfargo.com.INVALID.
Eric,

Adding -clrf option at the end of openssl s_client -connect <server>:<port> -clrf gave a 200 OK response. 

Thanks a ton!

Bharath Kolla


-----Original Message-----
From: Eric Covener [mailto:covener@gmail.com] 
Sent: Monday, February 06, 2017 6:43 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Apache 2.2.32 failing F5 health check

On Mon, Feb 6, 2017 at 8:40 PM,  <Bh...@wellsfargo.com.invalid> wrote:
> broken apache httpd version 2.2.32:
>
> openssl s_client -connect <server>:<port> -pause
>
> when paused input this.
>
> GET /login/healthcheck/content_check.wecv HTTP/1.0
>
> Host: <server name>

s_client doesn't send CRLF unless you pass -crlf.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: [users@httpd] Apache 2.2.32 failing F5 health check

Posted by Eric Covener <co...@gmail.com>.
On Mon, Feb 6, 2017 at 8:40 PM,  <Bh...@wellsfargo.com.invalid> wrote:
> broken apache httpd version 2.2.32:
>
> openssl s_client -connect <server>:<port> -pause
>
> when paused input this.
>
> GET /login/healthcheck/content_check.wecv HTTP/1.0
>
> Host: <server name>

s_client doesn't send CRLF unless you pass -crlf.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

RE: [users@httpd] Apache 2.2.32 failing F5 health check

Posted by Bh...@wellsfargo.com.INVALID.
broken apache httpd version 2.2.32:
openssl s_client -connect <server>:<port> -pause
when paused input this.
GET /login/healthcheck/content_check.wecv HTTP/1.0
Host: <server name>

You get bad request back from apache httpd
HTTP/1.1 400 Bad Request
Working  apache httpd version 2.2.31:
openssl s_client -connect <server name>:<port> -pause
when paused input this.
GET /login/healthcheck/content_check.wecv HTTP/1.0
Host: <server name>

You get content_check.wecv page from webserver with http code 200.


Bharath Kolla

From: Daniel [mailto:dferradal@gmail.com]
Sent: Monday, February 06, 2017 1:50 PM
To: <us...@httpd.apache.org>
Subject: Re: [users@httpd] Apache 2.2.32 failing F5 health check

Oh really? Enable mod_dumpio and show us the GET from your F5 "pings".

2017-02-06 21:34 GMT+01:00 <Bh...@wellsfargo.com.invalid>>:
This issue is different from the CR LF issue. We checked for any delimiters/spaces etc. The F5 health checks work fine with 2.2.31 on the same server, without any change in the configuration, but when we upgrade to 2.2.32, apache reports a 400 error.

Bharath Kolla



-----Original Message-----
From: Eric Covener [mailto:covener@gmail.com<ma...@gmail.com>]
Sent: Saturday, February 04, 2017 5:00 PM
To: users@httpd.apache.org<ma...@httpd.apache.org>
Subject: Re: [users@httpd] Apache 2.2.32 failing F5 health check

On Sat, Feb 4, 2017 at 4:56 PM,  <Bh...@wellsfargo.com.invalid>> 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 application can be
> accessed with web server listen address, but when accessed through the
> VIP, it sends a 400. Any help in debugging this issue will be much appreciated.


Someone recently reported a subset of their F5 health checks were using LF line endings instead of CR LF.

--
Eric Covener
covener@gmail.com<ma...@gmail.com>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org<ma...@httpd.apache.org>
For additional commands, e-mail: users-help@httpd.apache.org<ma...@httpd.apache.org>



--
Daniel Ferradal
IT Specialist

email         dferradal at gmail.com<http://gmail.com>
linkedin     es.linkedin.com/in/danielferradal<http://es.linkedin.com/in/danielferradal>

Re: [users@httpd] Apache 2.2.32 failing F5 health check

Posted by Daniel <df...@gmail.com>.
Oh really? Enable mod_dumpio and show us the GET from your F5 "pings".

2017-02-06 21:34 GMT+01:00 <Bh...@wellsfargo.com.invalid>:

> This issue is different from the CR LF issue. We checked for any
> delimiters/spaces etc. The F5 health checks work fine with 2.2.31 on the
> same server, without any change in the configuration, but when we upgrade
> to 2.2.32, apache reports a 400 error.
>
> Bharath Kolla
>
>
>
> -----Original Message-----
> From: Eric Covener [mailto:covener@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,  <Bh...@wellsfargo.com.invalid>
> 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 application can be
> > accessed with web server listen address, but when accessed through the
> > VIP, it sends a 400. Any help in debugging this issue will be much
> appreciated.
>
>
> Someone recently reported a subset of their F5 health checks were using LF
> line endings instead of CR LF.
>
> --
> Eric Covener
> covener@gmail.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>


-- 
*Daniel Ferradal*
IT Specialist

email         dferradal at gmail.com
linkedin     es.linkedin.com/in/danielferradal

RE: [users@httpd] Apache 2.2.32 failing F5 health check

Posted by Bh...@wellsfargo.com.INVALID.
This issue is different from the CR LF issue. We checked for any delimiters/spaces etc. The F5 health checks work fine with 2.2.31 on the same server, without any change in the configuration, but when we upgrade to 2.2.32, apache reports a 400 error.

Bharath Kolla



-----Original Message-----
From: Eric Covener [mailto:covener@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,  <Bh...@wellsfargo.com.invalid> 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 application can be 
> accessed with web server listen address, but when accessed through the 
> VIP, it sends a 400. Any help in debugging this issue will be much appreciated.


Someone recently reported a subset of their F5 health checks were using LF line endings instead of CR LF.

--
Eric Covener
covener@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: [users@httpd] Apache 2.2.32 failing F5 health check

Posted by Eric Covener <co...@gmail.com>.
On Sat, Feb 4, 2017 at 4:56 PM,  <Bh...@wellsfargo.com.invalid> 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 application can be accessed with web server listen
> address, but when accessed through the VIP, it sends a 400. Any help in
> debugging this issue will be much appreciated.


Someone recently reported a subset of their F5 health checks were
using LF line endings instead of CR LF.

-- 
Eric Covener
covener@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: [users@httpd] Apache 2.2.32 failing F5 health check

Posted by Luca Toscano <to...@gmail.com>.
Hi!

2017-02-04 22:56 GMT+01:00 <Bh...@wellsfargo.com.invalid>:

> 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 listen
> address, but when accessed through the VIP, it sends a 400. Any help in
> debugging this issue will be much appreciated.
>

please check
https://httpd.apache.org/docs/2.2/mod/core.html#httpprotocoloptions, it is
probably the root cause.

Thanks!

Luca