You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@guacamole.apache.org by "Mathijs (Jira)" <ji...@apache.org> on 2026/08/27 14:35:00 UTC

[jira] [Created] (GUACAMOLE-2324) Re-introduce "tight" encoding in the default encodings list

Mathijs created GUACAMOLE-2324:
----------------------------------

             Summary: Re-introduce "tight" encoding in the default encodings list
                 Key: GUACAMOLE-2324
                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-2324
             Project: Guacamole
          Issue Type: Improvement
            Reporter: Mathijs


We recently encountered some issues with users not being able to use our guacamole setup to connect to their VNC server. Apparently, their server only supported "tight" encoding. Per [this message from 2016|https://www.mail-archive.com/user@guacamole.incubator.apache.org/msg00007.html], this has been removed from the default encodings string in guacamole to prevent connections with JPEG compression in between, which hurts guacamole's own PNG compression.

In libvncclient the default encodings string (which is used if not explicitly specified by the user) still includes "tight".

In our case the user could explicitly ask for "tight" encoding and it would work, albeit with bad performance because indeed in this case JPEG was used by their server, because guacamole advertises this by default (because it is libvncclient's default to allow JPEG).

I'll be providing a PR to re-introduce tight in the default encodings string, while disabling JPEG by default.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)