MultiHTTPClient currently does not support request retries out of the box, which makes connections to backend services more brittle than necessary. This is especially the case where those backend services are contacted directly via LVS, as there is no retry at all in that situation.
The retry functionality should
- be limited to specific, configurable status codes,
- implement exponential delay & be limited to a small number (1-2 at most).