request for help: https reverse proxy ... or get more debug info from engine.io

[ericmandel]

Using v4, I am trying to implement a reverse proxy from an Apache web server to a socket.io server where https is configured on both (the simpler http case has always worked, as far back as v2.) Requests seem to be passed to the socket.io server (and indeed, long-polling works fine), but it looks like an upgrade header might be missing when the initial websocket request is made, as shown below:

env DEBUG='*' node js9Helper.js:

I would greatly appreciate help understanding what is going on here ... or help in getting additional debug info on what engine.io is receiving ...

Is it known that https can be used to reverse proxy to a socket.io server? My Apache configuration is shown below, and obviously I have tried both the old and new style techniques:

Thanks,

Eric