Whenever we use a HttpClient in the Gateway we need to make sure that all appropriate proxy settings are set on that HttpClient instance.
There is a HttpClientFactory that will set both proxy and proxy authentication settings on a newly created HttpClient instance.
Here is a (possibly incomplete) list of classes that create new instances of HttpClient on their own:
sgf.gateway.cim.harvest.feed.impl.LinkCIMDocumentExtractor.java
sgf.gateway.main.security.HttpClient301CertificateRequest.java
sgf.gateway.saml.attr.service.impl.esg.RemoteAttributesServiceProxySamlSoapImpl.java
sgf.gateway.service.datanode.impl.AbstractDataNodeClient.java
sgf.gateway.web.remoting.query.httpinvoker.client.HttpClientFactoryBean.java
Setting to Blocker because of BADCs need for running the Gateway behind a proxy.
There is a HttpClientFactory that will set both proxy and proxy authentication settings on a newly created HttpClient instance.
Here is a (possibly incomplete) list of classes that create new instances of HttpClient on their own:
sgf.gateway.cim.harvest.feed.impl.LinkCIMDocumentExtractor.java
sgf.gateway.main.security.HttpClient301CertificateRequest.java
sgf.gateway.saml.attr.service.impl.esg.RemoteAttributesServiceProxySamlSoapImpl.java
sgf.gateway.service.datanode.impl.AbstractDataNodeClient.java
sgf.gateway.web.remoting.query.httpinvoker.client.HttpClientFactoryBean.java
Setting to Blocker because of BADCs need for running the Gateway behind a proxy.
- is related to
-
GTWY-1864 Unable to add Harvesting job
- Done