Skip to main content
Best Answer

FME and the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables

  • April 5, 2018
  • 6 replies
  • 212 views
G

I have experienced that setting (windows) system variables HTTP_PROXY and HTTPS_PROXY overrides the proxy settings in (some parts of) FME Workbench / Server. For example the HTTPCaller seems to use the proxy settings from the HTTP_PROXY and HTTPS_PROXY system variables, even if the options in FME Workbench are different. The same is described in the GML Reader's documentation. In this documentation is stated that the GML reader follows up on the http_proxy environment variable.

When I do set these variables then the HTTPCaller transformer (and the FMEServerJobSubmitter) is not able to reach local adresses anymore (it will try to use the proxy for everything). Even if I fill provide a bypass list in NO_PROXY. For example, then FME Server's dashboard statistics gathering workspaces do not work. So it seems to ignore the NO_PROXY variable.

I need to set the HTTP_PROXY, HTTPS_PROXY and NO_PROXY enviroment variables because some of my own (embedded) Python scripts use them. For example Python's Requests module does this by default. So I am looking for a configuration where I can set HTTP_PROXY, HTTPS_PROXY and NO_PROXY variables, and still be able to reach local adresses using the HTTPCaller.

Best answer by rahulsharma

@gertjangj87, Our dev team has confirmed that HTTPCaller should fully support Environment Variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY.

For NO_PROXY environment variable should be a list of hostname separated via ','.

Can you confirm that it works for you?

NOTE: This is correct NO_PROXY values serveraname1, servername2, and so-on.

If you have prefix http://servername -- It will not work.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

6 replies

P
Forum|alt.badge.img
  • peterx
  • June 26, 2018
I'm using Python's Requests module, but it seems to not be using the Proxy. Any thoughts?

 

 

rahulsharma
Safer
Forum|alt.badge.img+10

@gertjangj87 HTTPCaller should honor all HTTP_* environment variables. For some reason, the NO_PROXY variable is currently not honored. I have filed an internal bug report on this and will update once we have this fixed.

rahulsharma
Safer
Forum|alt.badge.img+10
  • rahulsharmaSafer
  • Safer
  • Best Answer
  • July 25, 2018

@gertjangj87, Our dev team has confirmed that HTTPCaller should fully support Environment Variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY.

For NO_PROXY environment variable should be a list of hostname separated via ','.

Can you confirm that it works for you?

NOTE: This is correct NO_PROXY values serveraname1, servername2, and so-on.

If you have prefix http://servername -- It will not work.

carsonlam
Safer
Forum|alt.badge.img+7
  • carsonlamSafer
  • Safer
  • July 26, 2018
I'm using Python's Requests module, but it seems to not be using the Proxy. Any thoughts?

 

 

Requests should use these environment variables, if present. If FME Workbench is set to use system proxy settings, then Workbench will try to get the needed values and set these environment variables for FME's Python.
G
  • gertjangj87
  • Author
  • July 27, 2018
@rahulsharma

Thanks for your reaction on my request. I did use the http(s) prefix within the the NO_PROXY variable. So i suppose that's the reason why the configuration did not work at our servers. At this moment I have removed all proxy variables from the configuration. I will set these parameters again as soon as i find some time to test / experiment. I will inform you about the results.

rahulsharma
Safer
Forum|alt.badge.img+10
@rahulsharma

Thanks for your reaction on my request. I did use the http(s) prefix within the the NO_PROXY variable. So i suppose that's the reason why the configuration did not work at our servers. At this moment I have removed all proxy variables from the configuration. I will set these parameters again as soon as i find some time to test / experiment. I will inform you about the results.

Sure thing, please let us know if you still have any issues using these environment variables.

 

 

Community Stats

32,184
Posts
122,181
Replies
39,856
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.