You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running against a v3.1.x server, there is only rencode and bencode packet encoders available and so the server chooses bencode.
info-response packets trigger a network parsing error because the network parsing code in the html5 client has been re-worked to prefer rencodeplus (#3229) and not use rencode (too many unfixable problems).
This is not easily fixable - especially in an EOL branch. Potential solutions:
don't send info-response packets with bencode (+ html5 client?)
add rencodeplus to the v3.1.x branch
The text was updated successfully, but these errors were encountered:
The commit above adds rencodeplus - this may still be reverted if this causes problems.
For a start, this also required a fix to the v5.x branch of the html5 client: Xpra-org/xpra-html5@67259c4
When running against a v3.1.x server, there is only
rencode
andbencode
packet encoders available and so the server choosesbencode
.info-response
packets trigger a network parsing error because the network parsing code in the html5 client has been re-worked to preferrencodeplus
(#3229) and not userencode
(too many unfixable problems).This is not easily fixable - especially in an EOL branch. Potential solutions:
info-response
packets withbencode
(+html5
client?)rencodeplus
to the v3.1.x branchThe text was updated successfully, but these errors were encountered: