You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2016/07/19 09:21:53 UTC

[Bug 59884] New: [http(s)]]A failed ping must put an origin in an error state.

https://bz.apache.org/bugzilla/show_bug.cgi?id=59884

            Bug ID: 59884
           Summary: [http(s)]]A failed ping must put an origin in an error
                    state.
           Product: Apache httpd-2
           Version: 2.4.20
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: mod_proxy
          Assignee: bugs@httpd.apache.org
          Reporter: de.techno@gmail.com

The ping= property does not have any relevance.

If the ping fails (tested over HTTP where the webserver has been SIGSTOPed),
the backend is not set in an error state. As a result Apache assumes that the
bad backend is still healthy.

Also I would expect the ping to test if the backend is healthy before sending
the request to it. If the ping fails, the request must switch to another
backend. But this doesn't happen (because the origin is not set to an error
state).

-- 
You are receiving this mail because:
You are the assignee for the bug.

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