Hi Keni (@kenime ),
I did some extra tests, and I have the impression that the reverse proxy library (which I'm using behind the scenes) does something not correctly. Or I am not using it correctly somehow...
When I navigate in Chrome to my reverse-proxy node (which redirects me to httpbin.org), then I see e.g. server:nginx in the response headers:
I did expect to see server:Express, since Node-RED (and also the reverse proxy node) is running ExpressJs. But now Nginx is leaked, which is the webserver used to host httpbin.org ;-(
Don't see what could be going wrong. Unless somebody else can give me the golden tip, I am going to rename my node to e.g. node-red-contrib-http-redirect. I have developed this node mainly for redirecting my mjpeg streams via Node-RED, and that seems to be working fine ...
[EDIT] I'm wondering now if I should have used RedBird, which seems to be a reverse proxy build on top of node-http-proxy. Not sure anymore ...
