should help you out Turns out, if one wants to proxy websockets through an https proxy, one should make the proxy part normal websockets (ws://) not secure web sockets (wss://) which makes sense as the https proxy would have handled the ssl portion already and there is nothing to do.
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.