Bug 59884 - [http(s)]]A failed ping must put an origin in an error state.
Summary: [http(s)]]A failed ping must put an origin in an error state.
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.4.20
Hardware: PC Linux
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-19 09:21 UTC by dE
Modified: 2016-07-19 09:21 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dE 2016-07-19 09:21:53 UTC 
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).