Is there a way to bypass a forwarding proxy from a Javascript extension

[#1]

When on premises Edge is configured to use a forwarding proxy in the “/instal-dir/apigee4/conf/apigee/message-processor/http.properties” file.

We are able to bypass the forward proxy using the Service Callout and Target Connection with the “use.proxy=false” properties.

However we have not been able to bypass the forwarding proxy from the HTTPClient in Javascript.

Is there an option to bypass the forwarding proxy from the Javascript extension?

Already aware of this post at how to bypass forwarding proxies but the article does not mention the Javascript extension and HTTPClient object.

[#2 · Accepted solution]

Hi @James Beninghaus

Pls refer this https://community.apigee.com/questions/18582/configuring-the-javascript-object-model-to-use-a-w.html which talks about the same problem

As mentioned in that thread, APIRT-2587 enhancement (Internal) ticket will address this.

[#3]

Our implementation of the httpClient is not proxy aware/enabled. There are specific changes to be made to support proxies. Having said that - within the node environment you could use the node http client which allows you to connect to your proxy specifying the eventual host and path in header values. Come to think of it - this approach MAY work in your case James. Try something like this:

var http = require("http"),options = {
  host: "proxy.hostname.com",
  port: 8080,
  path: "http://weather.yahooapis.com/forecastrss?w=2423945",
  headers: {
    Host: "weather.yahooapis.com"
  }
}; 

I would try myself but don't have ready access to an environment with a proxy server...

[musivakumar]

can some one answer this question? @Dino