1 files changed, 48 insertions, 0 deletions
diff --git a/results/classifier/118/vnc/1732671 b/results/classifier/118/vnc/1732671
new file mode 100644
index 000000000..1a68ba3a5
--- /dev/null
+++ b/results/classifier/118/vnc/1732671
@@ -0,0 +1,48 @@
+vnc: 0.964
+network: 0.888
+socket: 0.871
+device: 0.785
+virtual: 0.775
+mistranslation: 0.768
+semantic: 0.682
+graphic: 0.678
+architecture: 0.632
+register: 0.594
+performance: 0.575
+files: 0.509
+ppc: 0.507
+user-level: 0.479
+risc-v: 0.458
+kernel: 0.456
+hypervisor: 0.452
+permissions: 0.434
+PID: 0.434
+VMM: 0.421
+debug: 0.381
+KVM: 0.378
+boot: 0.365
+peripherals: 0.356
+TCG: 0.354
+assembly: 0.299
+arm: 0.292
+i386: 0.254
+x86: 0.215
+
+vnc websocket compatibility issue
+
+WebSocket support in VNC should allow access from VNC client through upgraded WebSocket connection. This feature is not working in IE 11/Edge with noVNC HTML5 client, in contrast to that in Firefox/Safari, etc.
+
+The reason that IE 11/Edge fails to accept the connection upgrade is that the value equality of the `Upgrade` header field is checked in a strict case-sensitive manner in QEMU side, however, the IE/Edge does not send the exactly same string value `websocket` but a capital letter `W` instead.
+
+Defined in section 4.2.1 of rfc6455, the upgrade header field shall be treated case-insensitively.
+
+A patch shall be made in `io/channel-websock.c`, converting the value of upgrade string to lowercase before comparison is made with QIO_CHANNEL_WEBSOCK_UPGRADE_WEBSOCKET, to allow case-insensitive comparison in the process.
+
+Which version of QEMU did you test this against ?  It should be fixed in current GIT master AFAIK
+
+I think it should have been fixed in 33badfd.
+
+Sorry for the noise.
+
+No problem, it is a valid bug report, since we've not actually released the fix yet, so changing status.
+