xpra icon
Bug tracker and wiki

#1820 closed defect (worksforme)

HTML5 is slow on startup, showing ERR_INVALID_HTTP_RESPONSE

Reported by: stdedos Owned by: Antoine Martin
Priority: minor Milestone: 2.3
Component: html5 Version: 2.2.x
Keywords: Cc:

Description (last modified by Antoine Martin)

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

Attachments (4)

xpra-web-client-slow.png (20.5 KB) - added by stdedos 16 months ago.
xpra-html5-xterm.log (10.5 KB) - added by stdedos 16 months ago.
xpra-log-direct-to-app.log (251.9 KB) - added by stdedos 16 months ago.
xpra-log-first-connect.log (158.9 KB) - added by stdedos 16 months ago.

Download all attachments as: .zip

Change History (9)

Changed 16 months ago by stdedos

Attachment: xpra-web-client-slow.png added

Changed 16 months ago by stdedos

Attachment: xpra-html5-xterm.log added

comment:1 Changed 16 months ago by Antoine Martin

Description: modified (diff)
Milestone: 2.3
Owner: changed from Antoine Martin to stdedos

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.

comment:2 Changed 16 months ago by 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=0.0.0.0:14500 --html=on --start-child=xterm --exit-with-children=yes (Server is on the 172.16.57.0/24 network).

Then, from 10.36.143.0/24 network connect (172.16.57.108:14500).

I will provide the logs tomorrow.

comment:3 Changed 16 months ago by 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:

  • from the same machine that runs the server
  • using different browsers - and specify which one have problems
Last edited 16 months ago by Antoine Martin (previous) (diff)

Changed 16 months ago by stdedos

Attachment: xpra-log-direct-to-app.log added

Changed 16 months ago by stdedos

Attachment: xpra-log-first-connect.log added

comment:4 Changed 16 months ago by stdedos

Owner: changed from stdedos to Antoine Martin

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?

comment:5 Changed 16 months ago by Antoine Martin

Resolution: worksforme
Status: newclosed
Note: See TracTickets for help on using tickets.