From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Eric Blake" <eblake@redhat.com>, "Brian Rak" <brak@vultr.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/3] Improve websock response / error handling
Date: Fri, 8 Sep 2017 14:58:28 +0100 [thread overview]
Message-ID: <20170908135831.10556-1-berrange@redhat.com> (raw)
A followup of:
v1: https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg01176.html
v2: https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg01974.html
Changed in v3:
- Use strftime instead of g_date_time_format
Changed in v2:
- Drop redundant return statement
- Drop redundant variable initialization
- Assert that g_date_time_format is non-NULL
Daniel P. Berrange (3):
io: send proper HTTP response for websocket errors
io: include full error message in websocket handshake trace
io: use case insensitive check for Connection & Upgrade websock
headers
io/channel-websock.c | 195 ++++++++++++++++++++++++++++++++++++++-------------
io/trace-events | 2 +-
2 files changed, 146 insertions(+), 51 deletions(-)
--
2.13.5
next reply other threads:[~2017-09-08 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 13:58 Daniel P. Berrange [this message]
2017-09-08 13:58 ` [Qemu-devel] [PATCH v3 1/3] io: send proper HTTP response for websocket errors Daniel P. Berrange
2017-09-08 16:14 ` Philippe Mathieu-Daudé
2017-09-08 13:58 ` [Qemu-devel] [PATCH v3 2/3] io: include full error message in websocket handshake trace Daniel P. Berrange
2017-09-08 13:58 ` [Qemu-devel] [PATCH v3 3/3] io: use case insensitive check for Connection & Upgrade websock headers Daniel P. Berrange
2017-09-08 14:28 ` [Qemu-devel] [PATCH v3 0/3] Improve websock response / error handling no-reply
2017-09-08 14:32 ` Daniel P. Berrange
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=20170908135831.10556-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=brak@vultr.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).