Issue with Node.js when we use with company proxy

Google Cloud Apigee
1

I am trying to loadgen to generate traffic data in one of our system.

https://github.com/DinoChiesa/se-partner-bootcamp/tree/master/loadgen. - loadgen tool

We were able to successfully test from the command line, but through edge it failed with “socket hang up” issue.

Later we figured out that it could be due to company proxy and Dino(Developer of the tool) has enabled the node.js script to work with company proxy.

https://github.com/DinoChiesa/Edge-Runload-Proxy.

Now, we are facing an issue of 403, when we test loadgen(node.js script) from the command line as well as when we deploy in EDGE.

If anyone has used this loadgen proxy or faced this kind of issue with any other node.js proxy. please provide some pointers to solve the issue.

2 Likes
2

Hi Thrilochana,

The code 403 implies “Forbidden”; the server is receiving the request but denying access.

Which server? It’s not clear. It could be the proxy server that you are connecting through. It could be the target server. In either case, you should check:

  • do you have access?
  • are you passing the correct credentials? Some proxy servers require credentials.

The problem you are describing seems to have nothing to do with nodejs or the loadgen script.

3

Hi Dino,

yes, it is at proxy. I have access to proxy and don’t need any credentials for proxy.

Thanks, Thrilochana