Mailing List Archive

[Bug 64810] New: Unable to proxy requests to a secured websockets (wss) in 2.4.41
https://bz.apache.org/bugzilla/show_bug.cgi?id=64810

Bug ID: 64810
Summary: Unable to proxy requests to a secured websockets (wss)
in 2.4.41
Product: Apache httpd-2
Version: 2.4.41
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_proxy_wstunnel
Assignee: bugs@httpd.apache.org
Reporter: onengballon@gmail.com
Target Milestone: ---

I have the following setup for a vnc service:
- vnc client : noVNC (0.6.1)
- vnc server : libvncserver (0.9.12)

When the noVNC client is launched, it will be re-directed and be served over
secured layer, 'https://host/novnc.html?path=vnc'. Then this connection will be
proxy'd to 'wss://localhost:5901': ProxyPass /vnc wss://localhost:5901/
Then the expected upgraded to a websocket connection will happen.

In 2.4.41, the vnc server acknowledges a TLS/SSL Websockets Connection but then
it will eventually report an 'invalid client header'. Also used noVNC 1.1.0
client and this issue is still encountered.
This was working since 2.4.29, up until 2.4.39. Also tested using the recent
release - 2.4.46, and this wss connection still happens.

Best regards.

--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org