https://bz.apache.org/bugzilla/show_bug.cgi?id=64810
--- Comment #4 from Orlando Ballon <[email protected]> --- Thank you for the information. I set the "SSLProxyCheckPeerName off" in the httpd.conf and it does resolve the issue. Below is the workflow of my vnc service setup: 1. Launch my site over http, and starts the vnc server (libvncserver). 2. click a button to launch noVNC client. 3. The url will be re-directed and be served over https, 'https://host/novnc.html?path=vnc'. 4. This will be proxy'd to 'wss://localhost:5901' per httpd.conf : ProxyPass /vnc wss://localhost:5901/ 5. A prompt to accept a security exception to the site will show, and accepting the exception, the 'wss' connection will be a success. However, when I launched my site over https, the vnc connection over wss will fail. So, in step #1, the site is launched over https, and a prompt to accept a security exception to the site will show. After accepting the exception, step #5 will not prompt anymore but the vnc connection will fail. Have no details yet on this case but when I use the reverted option, this case where the site is launched over https, will still have a successful vnc connection over wss. That's all for now. Thanks. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
