You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2019/10/04 20:51:00 UTC

[jira] [Closed] (GUACAMOLE-891) Guacamole's RDP printer doesn't work if the UI lang of RDP host system is Russian and nginx reverse proxy is used

     [ https://issues.apache.org/jira/browse/GUACAMOLE-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Jumper closed GUACAMOLE-891.
---------------------------------
    Resolution: Invalid

> Guacamole's RDP printer doesn't work if the UI lang of RDP host system is Russian and nginx reverse proxy is used
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-891
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-891
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole
>    Affects Versions: 1.0.0
>            Reporter: Eugene / Dae
>            Priority: Minor
>
> Guacamole's RDP printer will not work if:
>  # the user interface (or system) language of RDP host system is Russian;
>  # nginx reverse proxy is used with proxy_pass directive pointing to Guacamole's Tomcat URL.
> Instead, the browser sends a request to download the PDF that fails in Tomcat with code 400.
> If you change the UI language of RDP host to English, everything works fine, as well as if you connect to Tomcat directly (without nginx).
> This nginx config will cause the said problem:
> {{location /guacamole {}}
>  {{proxy_pass [http://192.168.1.1/guacamole/];}}
>  {{}}}
> But the following config will *NOT* cause the said problem:
> {{location /guacamole {}}
>  {{proxy_pass [http://192.168.1.1|http://192.168.1.1/];}}
>  {{}}}
> Here's what is logged:
> {{guac guacd: Print job created}}
>  {{guac guacd: Created PDF filter process PID=442}}
>  {{guac guacd: Running gs}}
>  {{guac: org.apache.coyote.http11.AbstractHttp11Processor process}}
>  {{guac: INFO: Error parsing HTTP request header}}
>  {{guac: Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.}}
>  {{guac: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986}}
> We've been able to reproduce this on three separate installations of Guacamole 1.0.0 on CentOS and Ubuntu Server with three separate RDP hosts running Windows Server 2016 and 2019.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)