The POCO C++ Libraries are powerful cross-platform C++ libraries for building network- and internet-based applications that run on desktop, server, mobile, IoT, and embedded systems.
Describe the bug
Exposing vscode-server (uses websockets for initialization) through this listener just returns 401 unauthorized for all websocket handshakes (according to a webkit browser, firefox doesn't show this kind of info).
I have no idea how to even approach debugging this. It's sadly quite an annoying setup to begin with, due to the way docker works. Caddy shouldn't interfere, since it's working fine without my proxy in front.
To Reproduce
Set the project up according to the readme and make it accessible through caddy, or another reverse-proxy (required for this whole thing to work) and put vscode-server behind the poco proxy
Logs
container-power-proxy | client -> server (length=104, flags=0x82).
container-power-proxy | cl I/O error: Operation now in progress # I don't think these errors change anything. Simply returning the data sent from the client also returns the same error
container-power-proxy | server -> client (length=104, flags=0xc2).
container-power-proxy | sv I/O error: Operation now in progress
container-power-proxy | client -> server (length=0, flags=0x0).
Describe the bug Exposing vscode-server (uses websockets for initialization) through this listener just returns 401 unauthorized for all websocket handshakes (according to a webkit browser, firefox doesn't show this kind of info).
I have no idea how to even approach debugging this. It's sadly quite an annoying setup to begin with, due to the way docker works. Caddy shouldn't interfere, since it's working fine without my proxy in front.
To Reproduce Set the project up according to the readme and make it accessible through caddy, or another reverse-proxy (required for this whole thing to work) and put vscode-server behind the poco proxy
Logs
Please add relevant environment information: