xpra icon
Bug tracker and wiki

Changes between Initial Version and Version 1 of Ticket #2121, comment 24


Ignore:
Timestamp:
02/08/19 03:01:21 (9 months ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2121, comment 24

    initial v1  
    1 Replying to [comment:22 Antoine Martin]:
    2 > > After r21560, when connecting from either client I'm now getting the server-side error:
    3 > > (..)
    4 > > {{{invalid packet header, HTTP GET request}}}
    5 > That's very odd. Works just fine here.
    6 >
    7 > Please post the exact commands you are using for testing.
    8 > And maybe also the proxy's {{{-d proxy}}} log and the server's {{{-d websocket,http}}} log.
    9 >
    10 > For reference, here's what I am using for testing:
    11 > * server:
    12 > {{{
    13 > xpra start  --start=xterm  --no-daemon -d websocket,http
    14 > }}}
    15 > * proxy:
    16 > {{{
    17 > xpra proxy --no-daemon --bind-tcp=0.0.0.0:14501 --tcp-auth=none
    18 > }}}
    19 > * client:
    20 > {{{
    21 > xpra attach ws://localhost:14501 -d websocket
    22 > }}}
    23 
    241Something was fixed in a later release, can't reproduce on head.
    25 Looked like html was getting copied into /usr/share/dist/xpra instead of /usr/share/xpra. Not an issue now though.
     2Looked like html was getting copied into {{{/usr/share/dist/xpra}}} instead of {{{/usr/share/xpra}}}. Not an issue now though.
    263
    274From a quick test new websocket work looks very good, thanks!