Public bug reported:
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.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715186
Title:
websockets: Improve error messages
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1715186/+subscriptions
