vnc: 0.970 socket: 0.959 network: 0.826 other: 0.822 device: 0.760 graphic: 0.752 semantic: 0.732 KVM: 0.673 instruction: 0.555 boot: 0.537 assembly: 0.398 mistranslation: 0.376 websockets: Improve error messages Since 2.9 / 07e95cd529af345fdeea230913f68eff5b925bb6 , whenever the VNC websocket server finds an error with the incoming connection request, it just closes the socket with no further information. This makes figuring out what's wrong with the request nearly impossible. I would be nice if: * HTTP 400 were returned to the client, with an appropriate error message * Maybe something written to the log as well? Currently, I'm resorting to looking at my request and the websocket source and hoping I can figure out what's wrong. At very least we should also use 404 if given a invalid path Will be included for 2.11 in commit 3a3f8705962c8c8a47a9b981ffd5aab7274ad508 Author: Daniel P. Berrange