websockets: Improve error messages
Bug #1715186 reported by
Brian Rak
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Since 2.9 / 07e95cd529af345
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.
Changed in qemu: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
At very least we should also use 404 if given a invalid path