[
https://issues.apache.org/jira/browse/GUACAMOLE-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047912#comment-17047912
]
Mike Jumper commented on GUACAMOLE-972:
---------------------------------------
{quote}
I have HTTPS enabled on a Tomcat that is directly exposed with no reverse
proxies in between. File uploads on RDP fail with an "internal error" appearing
on the client almost immediately after starting. Looking at browser DevTools is
not yielding any clues as to why - there's only a net::ERR_CONNECTION_RESET.
The request appears to be correctly formatted and uses HTTPS and the correct
port.
{quote}
My guess would be that:
* This is not a bug in Guacamole, nor an issue specific to 1.1.0.
* The relevant connector in the Tomcat settings is configured with a maximum
request body size which is effectively blocking your upload attempt.
I'd recommend checking the connector and its settings (including defaults). If
things still don't work, please post to the [email protected] mailing
list rather than open a new issue here. Something which works with HTTP but not
HTTPS is unlikely to be a bug in Guacamole, nor is it likely that Guacamole has
a bug which prevents its use over HTTPS (this would have been tested prior to
release and is how Guacamole is used in production).
{quote}
Posting this here even though I can't pinpoint the exact cause yet so that this
makes it into 1.2.0 if need be...
{quote}
Scope of 1.2.0 has already been set.
> RDP file upload fails with HTTPS on for Tomcat
> ----------------------------------------------
>
> Key: GUACAMOLE-972
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-972
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-client
> Affects Versions: 1.1.0
> Reporter: Joonas Tuomisto
> Priority: Minor
>
> I'm testing 1.1.0 and came across this issue...
>
> I have HTTPS enabled on a Tomcat that is directly exposed with no reverse
> proxies in between. File uploads on RDP fail with an "internal error"
> appearing on the client almost immediately after starting. Looking at browser
> DevTools is not yielding any clues as to why - there's only a
> net::ERR_CONNECTION_RESET. The request appears to be correctly formatted and
> uses HTTPS and the correct port.
>
> Connecting to HTTP instead of HTTPS, (i.e. 8080 instead of 8443) everything
> works fine.
>
> This used to work previously in 1.0.0 albeit I can't directly compare since
> up until now I've been using Fedora and the distro-provided Tomcat and now
> I'm testing with CentOS 8 + Apache upstream Tomcat with EPEL 8 tomcat-native.
> The server/tomcat configurations however are identical.
>
> Posting this here even though I can't pinpoint the exact cause yet so that
> this makes it into 1.2.0 if need be...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
