Xpra: Ticket #1820: HTML5 is slow on startup, showing ERR_INVALID_HTTP_RESPONSE

Continuing from ticket:1813#comment:4

(*-with-children commands work as expected.)

There is a small delay and a "misleading" ERR_INVALID_HTTP_RESPONSE shown on Vivaldi.

Attached server logfile and screenshot. I am waiting the webpage from around 15:05:24,725 to 15:06:07,373

Server: xpra v2.3-r19012

Mon, 23 Apr 2018 12:21:03 GMT - stdedos: attachment set

Mon, 23 Apr 2018 12:21:10 GMT - stdedos: attachment set

Mon, 23 Apr 2018 12:33:30 GMT - Antoine Martin: owner, description changed; milestone set

The ERR_INVALID_HTTP_RESPONSE was fixed in r19057.

These are unexpected:

invalid packet format, HTTP GET request

HTTP packets should be forwarded to the websocket handler.

Please provide steps to reproduce and/or post the "-d network,websocket" server output.

Mon, 23 Apr 2018 12:52:16 GMT - stdedos:

Reproduce is easy for me. Although, it could be the network setup that's getting in the way and making the delays.

Locally this works in an instant ...

Simply, run the command: xpra start --bind-tcp= --html=on --start-child=xterm --exit-with-children=yes (Server is on the network).

Then, from network connect (

I will provide the logs tomorrow.

Mon, 23 Apr 2018 16:15:30 GMT - Antoine Martin:

I think I saw the bug once on Ubuntu 16.04, but never since. Once thing that stands out is that Ubuntu ships a really old version of websockify - this may be part of the problem. You may want to replace it with a newer version (0.8) from pypi instead. Please try connecting:

Fri, 27 Apr 2018 11:10:43 GMT - stdedos: attachment set

Fri, 27 Apr 2018 11:10:56 GMT - stdedos: attachment set

Fri, 27 Apr 2018 11:11:49 GMT - stdedos: owner changed

It seems, after updating to the latest beta I don't see that issue anymore.

However, I do see a lot of (handled?) exceptions.

Maybe something something depended on those?

Fri, 27 Apr 2018 12:20:40 GMT - Antoine Martin: status changed; resolution set

Sat, 23 Jan 2021 05:34:39 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1820