From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-devel@nongnu.org, Brian Rak <brak@vultr.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/2] io: send proper HTTP response for websocket errors
Date: Thu, 7 Sep 2017 10:13:33 +0100 [thread overview]
Message-ID: <20170907091333.GB30609@redhat.com> (raw)
In-Reply-To: <dac64b67-0fcf-73c2-2371-377f0a3fbb48@amsat.org>
On Wed, Sep 06, 2017 at 03:06:03PM -0300, Philippe Mathieu-Daudé wrote:
> Hi Daniel,
>
> On 09/06/2017 07:40 AM, Daniel P. Berrange wrote:
> > When any error occurs while processing the websockets handshake,
> > QEMU just terminates the connection abruptly. This is in violation
> > of the HTTP specs and does not help the client understand what they
> > did wrong. This is particularly bad when the client gives the wrong
> > path, as a "404 Not Found" would be very helpful.
> >
> > Refactor the handshake code so that it always sends a response to
> > the client unless there was an I/O error.
> >
> > Fixes bug: #1715186
> >
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > ---
> > io/channel-websock.c | 179 ++++++++++++++++++++++++++++++++++++++-------------
> > 1 file changed, 134 insertions(+), 45 deletions(-)
> >
> > diff --git a/io/channel-websock.c b/io/channel-websock.c
> > index 5a3badbec2..b9cc5a1371 100644
> > --- a/io/channel-websock.c
> > +++ b/io/channel-websock.c
> > @@ -44,13 +44,39 @@
> > #define QIO_CHANNEL_WEBSOCK_CONNECTION_UPGRADE "Upgrade"
> > #define QIO_CHANNEL_WEBSOCK_UPGRADE_WEBSOCKET "websocket"
> > -#define QIO_CHANNEL_WEBSOCK_HANDSHAKE_RESPONSE \
> > +#define QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_COMMON \
> > + "Server: QEMU VNC\r\n" \
> > + "Date: %s\r\n"
>
> and
> "Sec-WebSocket-Version: " \
> QIO_CHANNEL_WEBSOCK_SUPPORTED_VERSION "\r\n" \
This header is only supposed to be set in error responses,
not in the 101 response.
> or what about:
>
> #define QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_COMMON(conn) \
> "Server: QEMU VNC\r\n" \
> "Date: %s\r\n" \
> "Connection: " conn "\r\n" \
> "Sec-WebSocket-Version: " \
> QIO_CHANNEL_WEBSOCK_SUPPORTED_VERSION "\r\n"
I'm not a fan of parameterizing this - I think it is clearer
to see the full connection header inline below.
> > +
> > +#define QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_OK \
> > "HTTP/1.1 101 Switching Protocols\r\n" \
> > + QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_COMMON \
> > "Upgrade: websocket\r\n" \
> > "Connection: Upgrade\r\n" \
> > "Sec-WebSocket-Accept: %s\r\n" \
> > "Sec-WebSocket-Protocol: binary\r\n" \
> > "\r\n"
> > +#define QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_NOT_FOUND \
> > + "HTTP/1.1 404 Not Found\r\n" \
> > + QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_COMMON \
> > + "Connection: close\r\n" \
> > + "\r\n"
> > +#define QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_BAD_REQUEST \
> > + "HTTP/1.1 400 Bad Request\r\n" \
> > + QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_COMMON \
> > + "Connection: close\r\n" \
> > + "Sec-WebSocket-Version: 13\r\n" \
>
> drop
>
> > + "\r\n"
>
> or with previous macro:
>
> #define QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_BAD_REQUEST \
> "HTTP/1.1 400 Bad Request\r\n" \
> QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_COMMON("close") \
> "\r\n"
>
> > +#define QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_SERVER_ERR \
> > + "HTTP/1.1 500 Internal Server Error\r\n" \
> > + QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_COMMON \
> > + "Connection: close\r\n" \
> > + "\r\n"
> > +#define QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_TOO_LARGE \
> > + "HTTP/1.1 403 Request Entity Too Large\r\n" \
> > + QIO_CHANNEL_WEBSOCK_HANDSHAKE_RES_COMMON \
> > + "Connection: close\r\n" \
> > + "\r\n"
> > #define QIO_CHANNEL_WEBSOCK_HANDSHAKE_DELIM "\r\n"
> > #define QIO_CHANNEL_WEBSOCK_HANDSHAKE_END "\r\n\r\n"
> > #define QIO_CHANNEL_WEBSOCK_SUPPORTED_VERSION "13"
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-09-07 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 10:40 [Qemu-devel] [PATCH v1 0/2] Improve websockets server error reporting Daniel P. Berrange
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 [this message]
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=20170907091333.GB30609@redhat.com \
--to=berrange@redhat.com \
--cc=brak@vultr.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 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.