httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <Bharath.C.Ko...@wellsfargo.com.INVALID>
Subject RE: [users@httpd] Apache 2.2.32 failing F5 health check
Date Tue, 07 Feb 2017 01:40:00 GMT
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: <users@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 <Bharath.C.Kolla@wellsfargo.com.invalid<mailto:Bharath.C.Kolla@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<mailto:covener@gmail.com>]
Sent: Saturday, February 04, 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,  <Bharath.C.Kolla@wellsfargo.com.invalid<mailto:Bharath.C.Kolla@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<mailto:covener@gmail.com>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org<mailto:users-unsubscribe@httpd.apache.org>
For additional commands, e-mail: users-help@httpd.apache.org<mailto:users-help@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>
Mime
View raw message