This change is about supporting use cases where this reverse-proxy system needs to have its client counterpart going through an HTTPS_PROXY.
Having this configuration at the HttpClient level directly instead of per backends makes sense in deployment models where all or no backends need to go through the proxy, and never a subset of backends.
Description
This change is about supporting use cases where this reverse-proxy system needs to have its client counterpart going through an HTTPS_PROXY.
Having this configuration at the HttpClient level directly instead of per backends makes sense in deployment models where
all
orno
backends need to go through the proxy, and never a subset of backends.