http through proxy connection

[Jack_A.]

I ran into a similar issue and was able to workaround the proxy configuration by setting the all_proxy environment variable and then did not need make any changes to my LabVIEW code which uses the HTTP VIs.  The HTTP VIs are built on top of cURL.  Here's a page which talks about cURL's proxy options and the environment variables: https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html

Hope this helps the next person who has to deal with proxies.

[aartjan]

Jack,

Although I appreciate you make the effort of posting the solution, it is way too late for NI to come up with this. In the mean time several other parties started their own http toolkits. I can very much recommend the encryption compendium from LVS tools. This also covers NTLM proxy authentication.

Maybe the http toolkit can do much more than meets the eye due to the powerful cURL backend, but NI did a very good job hiding it from end users.

[titi_nicolas]

---

@Jack_A. wrote:

I ran into a similar issue and was able to workaround the proxy configuration by setting the all_proxy environment variable and then did not need make any changes to my LabVIEW code which uses the HTTP VIs.  The HTTP VIs are built on top of cURL.  Here's a page which talks about cURL's proxy options and the environment variables: https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html

Hope this helps the next person who has to deal with proxies.

---

I am sorry I don't understand where I should set the all_proxy environment variable.

I feel totally lost with this cURL stuff and the page you sent does not help me.

Could you explain please in more details ?

In the end, I would like to be able to capture the HTTP VIs using Fiddler.

But this (complex) field is really new to me which means my knowledge is zero.

[rolfk]

---

@titi_nicolas wrote:

---

@Jack_A. wrote:

I ran into a similar issue and was able to workaround the proxy configuration by setting the all_proxy environment variable and then did not need make any changes to my LabVIEW code which uses the HTTP VIs.  The HTTP VIs are built on top of cURL.  Here's a page which talks about cURL's proxy options and the environment variables: https://curl.haxx.se/libcurl/c/CURLOPT_PROXY.html

Hope this helps the next person who has to deal with proxies.

---

I am sorry I don't understand where I should set the all_proxy environment variable.

I feel totally lost with this cURL stuff and the page you sent does not help me.

Could you explain please in more details ?

In the end, I would like to be able to capture the HTTP VIs using Fiddler.

But this (complex) field is really new to me which means my knowledge is zero.

---

Ahh these young folks who never have looked under the hood of Windows or Macs. 🙂

Environment variables is something that exists in every OS somehow but is very hidden away under modern desktop operating systems.

libcurl, which is at the core of the NI HTTP library used by the various HTTP tools, however is originally a Unix library and there, environment variables are still quite commonplace even when you run a desktop environment on top of your Linux kernel.

Under Windows the environment variables are managed by the Windows kernel and can be modified through various means. The GUI method is described here: https://support.shotgunsoftware.com/hc/en-us/articles/114094235653-Setting-global-environment-variab....

The libcurl library queries specific environment variables to determine certain behaviour at runtime. Here is a list of possible environment variable settings that control libcurl: https://curl.se/libcurl/c/libcurl-env.html

Note that under Windows the names of environment variables is case insensitive and usually written as uppercase.