Proxy node for pekfinger-red

Usage

• app ( ) : Needs a app created for pekfinger-red web applications.
• Debug level ( ) : Set the debug level which will be shown on the server console.
• autostart ( ) : If your proxy settings are all strings, the proxy can start automatically on startup.
• url ( ) : Set the url path for the requests which should be proxied.
• target ( ) : target host to proxy to. (protocol + host).
• websocket ( ) : Activate to proxy websocket requests.
• customHeader (JSON) : Overwrite the header options. Set the parameter name as key. Only parameters set will be overwritten.

Advanced router function

If you need a more dynamic target, you can set a function in your msg which will have access to the req object. Example code where we need data from the requested url:

msg.payload = function (req) {
  if (req.url.startsWith('/shuttle/')) {
      const projects = flow.get('projects')    // Object where key is project name
      const urlProject = req.url.split('/')[2] // req.url is /shuttle/myProjectName
      if (urlProject)
      return 'http://127.0.0.1:' + projects[urlProject].port
  }
  return 'http://127.0.0.1'
}

return msg;

Developers

If you want to modify something inside the openApi-red.html file, I recommend to use SIR.

With help of SIR you can handle the p-red-proxy.svelte file in which the code is much cleaner and easier to handle.

Based on:

http-proxy-middleware