https://issues.apache.org/bugzilla/show_bug.cgi?id=54946
--- Comment #7 from Justin Honold <[email protected]> --- So I had run into this yesterday. For me it's disrupting the use of Varnish. I have a Rails + Passenger + httpd stack behind Varnish, and Varnish uses "probes" to check for site availability. The method we currently have in place is to render a blank page, which is sufficient to generate a 200 response. As it turns out, Varnish appears to care about the Reason-Phrase even if it receives a 200 - and now it doesn't have one, so Varnish thinks the apps are down. As a workaround I'm forcing them to be "healthy" in the admin console, but doing this prevents Varnish from detecting failure on a given app server. I mentioned to Eric I was on 2.2.24 on Amazon Linux/EC2, which is why he asked. I just downloaded their SRPM, and the patch at https://issues.apache.org/bugzilla/attachment.cgi?id=22019&action=diff is present via "httpd-2.2.3-r693108.patch," which references: https://bugzilla.redhat.com/show_bug.cgi?id=853128 (no access) http://svn.apache.org/viewvc?view=revision&revision=693108 http://svn.apache.org/viewvc?view=revision&revision=693224 So there's the smoking gun - at least for me. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
