Trying to get Websockify/noVNC to work through a reverse proxy

fixed the issue. Will look into that further To get accurate numbers one would have to benchmark this, and preferably with your architecture, software versions, and server. However think of it like this:
One ProxyPass rule causes one string comparison, probaby by using PCRE. All ProxyPassReverse rules cause string comparison (and potentially search & replace) against 5 header fields. Your production server can probably handle some 5+ million ProxyPass and 1+ million ProxyPassReverse operations per second.

ProxyPass        /website/test/            http://www.example:8080/web/test
ProxyPass        /website/test2/           http://www.example:8080/web/test2
ProxyPassReverse /website/                 http://www.example:8080/web

hope this fix your issue Did you follow this guide? https://github.com/kanaka/websockify/wiki/Compiling-Websockify-as-Windows-Executable
Websockify uses the python multiprocessing module. This module is problematic on Windows, especially with older versions of python. You might try python 3.2 or greater and see if you have more success although no guarantees. Websockify is developed and tested on Linux only.

it helps some times Apparently replacing 127.0.0.1 with localhost in the hello.js script did the trick. Not completely sure why (I guess it has something to do with my hosts file), but it works.

it fixes the issue I'm trying to get a very simple proxy working with node-http-proxy which I would expect to just return the contents of google: , You need to set the Host header of your request

const http = require('http');
const httpProxy = require('http-proxy');

const targetHost = 'www.google.co.uk';

const proxy = httpProxy.createProxyServer({
    target: 'http://' + targetHost
});

http.createServer(function (req, res) {
    proxy.web(req, res);

}).listen(6622);

proxy.on('proxyReq', function(proxyReq, req, res, options) {
    proxyReq.setHeader('Host', targetHost);
});

const proxy = require('express-http-proxy');
app.use('*', proxy('www.google.co.uk', {
  forwardPath: function(req, res) {
    return url.parse(req.originalUrl).path;
  }
}));

To fix this issue The application being loaded is set up to load assets from the server root, not with server root + /node2/