From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Brian Rak <brak@vultr.com>, "Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH v1 0/2] Improve websockets server error reporting
Date: Wed, 6 Sep 2017 11:40:41 +0100 [thread overview]
Message-ID: <20170906104043.30745-1-berrange@redhat.com> (raw)
The websockets server gives no useful error response to the client
nor provides any way to debug errors no the server
Daniel P. Berrange (2):
io: send proper HTTP response for websocket errors
io: include full error message in websocket handshake trace
io/channel-websock.c | 184 ++++++++++++++++++++++++++++++++++++++-------------
io/trace-events | 2 +-
2 files changed, 138 insertions(+), 48 deletions(-)
--
2.13.5
next reply other threads:[~2017-09-06 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 10:40 Daniel P. Berrange [this message]
2017-09-06 10:40 ` [Qemu-devel] [PATCH v1 1/2] io: send proper HTTP response for websocket errors Daniel P. Berrange
2017-09-06 18:06 ` Philippe Mathieu-Daudé
2017-09-07 9:13 ` Daniel P. Berrange
2017-09-06 10:40 ` [Qemu-devel] [PATCH v1 2/2] io: include full error message in websocket handshake trace Daniel P. Berrange
2017-09-06 18:06 ` Philippe Mathieu-Daudé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170906104043.30745-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=brak@vultr.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.