Closed maurimuchico-work closed 11 months ago
Duplicate of https://github.com/node-red/node-red/issues/4324
You need to raise this with the author of dialogflow-full-nodered, they have a broken dependency and they need to fix it.
$ npm list agent-base
broken@ /home/hardillb/temp/broken
└─┬ dialogflow-full-nodered@1.0.10
└─┬ dialogflow@0.7.0
└─┬ google-gax@0.20.0
├─┬ google-auth-library@2.0.2
│ └─┬ https-proxy-agent@2.2.4
│ └── agent-base@4.3.0
└─┬ grpc@1.24.11
└─┬ @mapbox/node-pre-gyp@1.0.11
└─┬ https-proxy-agent@5.0.1
└── agent-base@6.0.2
Thanks @hardillb for your quick response. You can close this ticket then. Regards
Current Behavior
When using an HTTPS URL, https://www.google.com/, in an HTTP request node it throws a connection refused error with the resolved address being 127.0.0.1. If you use the same domain but as non-secure, http://www.google.com/, it fetches from the correct address. This was previously reported and resolved here: https://github.com/node-red/node-red/issues/3072 and it's related with the community node: dialogflow-full-nodered. It's falling again since node-red 3.1.3 but it was working on node-red 3.0.2.
Expected Behavior
The call to the https server using an http request node should return a response in this case or a remote server error
Steps To Reproduce
Example flow
Environment