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: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, <bharath.c.ko...@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 cove...@gmail.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
