The current Guacamole protocol status codes do not accurately represent cases common to remote desktop connections, such as:
- The remote desktop server being unreachable
- The remote desktop server outright refusing the connection
- The user session timing out due to the remote desktop (not due to the guac client communication getting cut off)
- The user session getting kicked by the admin, by another user signing in, etc.
For the sake of downstream use of the libraries as well as for a good user experience, it's important that such cases are accurately forwarded down the pipeline to the client.