-
Type:
Enhancement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 21.0.0, Meridian-2016.1.8, Meridian-2017.1.1
-
Fix Version/s: 23.0.1, Meridian-2018.1.3
-
Security Level: Default (Default Security Scheme)
-
Labels:
-
Sprint:Horizon - August 8th 2018, Horizon - August 15th 2018, Horizon - August 22nd 2018, Horizon - August 29th 2018, Horizon - September 05 2018, Horizon - September 12 2018, Horizon - September 26 2018, Horizon - October 3rd 2018, Horizon - October 10th 2018, Horizon - October 17th 2018, Horizon - October 24th 2018
In some customer installations, I've seen a regular requirement of being able to route HTTP traffic through a Proxy.
When using Apache HTTP Client, the proxy settings should be part of the client, which means, our code should be changed in order to support proxy settings.
This would be useful for poller monitors like WebMonitor and PageSequenceMonitor. Of course, HTTP/XML Collector (and maybe WSMAN, as it uses HTTPS behind the scenes).
A concrete use case is the Remote Poller or a Minion that works behind a Proxy, and there are poller monitors and collection metrics that requires HTTP.
