Hi ,
We have installed edgemicro version 2.4.6 . Since our servers are behind the firewall we are using a http_proxy in the environment settings to let edgemicro communicate with APIgee edge to download the profiles & products . This all works fine and our edgemicro starts up really well .
But when the API calls are made to edgemicro it continues to use the http_proxy towards the targets which is not the desired behaviour . The edgemicro is in the same network as the target and hence we dont intend to route it via the http_proxy .
I need some suggestion on how to limit the http_proxy only for profile downloading and not for the actual API calls to target ?
I went through the following section " Setting up Edge Microgateway behind a company firewall" in page edgemicro
But still it does not help .
Please suggest .
/Hari
you should be able to use the NO_PROXY env var with a list of hostnames that don't have to go through the proxy.
Thanks Srinandans .I did that too but then the edgemicro does not start up .
But still I would prefer something which is a one time setup because excluding hosts using NO_PROXY needs a change for every new target getting added .
This PR: https://github.com/apigee/microgateway-core/pull/97 might help you. ETA 2.5.20-beta.
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |