You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by "Евгений Н. Жуков" <eu...@gmail.com> on 2023/01/05 23:12:41 UTC
Printing job with non-ASCII name thru nginx
Hi! Using 1.4 with nginx configured like
https://guacamole.apache.org/doc/gug/reverse-proxy.html
faced with issue printing when the job has Russian characters. The web
session stops working, catalina.out contain following error:
Invalid character found in the request target
[/guacamole/api/session/tunnels/420842f2-118b-42e6-8118-eb2144da6a32/streams/0/<C8D2D1209620C1EBEEEAEDEEF2>.pdf?token=E8ACB2365B3E87D63B487F17F198A16BF52D67E4F32A2EC87A5A52B8F5BA21FC
]. The valid characters are defined in RFC 7230 and RFC 3986
How to fix nginx config to correctly print from guacamole?
--
Eugene
Re: Printing job with non-ASCII name thru nginx
Posted by Nick Couchman <vn...@apache.org>.
On Fri, Jan 6, 2023 at 1:20 PM Евгений Н. Жуков <eu...@gmail.com> wrote:
>
> There is no issue with non-ASCII printing if guacamole published at the root of tomcat server (i.e. 192.168.1.9:8080/ istead 192.168.1.9:8080/guacamole
> I just deleted all content of webapp folder and renamed guacamole.war to ROOT.war
>
> пт, 6 янв. 2023 г. в 20:48, Евгений Н. Жуков <eu...@gmail.com>:
>>
>> Did some experiments, printing works fine with apache & IIS but not working with nginx.
You may want to post to the Nginx forum or mailing list if you
continue to have issues with this - if the problem is specific to
Nginx then that community will be best able to help you sort that out.
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: Printing job with non-ASCII name thru nginx
Posted by "Евгений Н. Жуков" <eu...@gmail.com>.
There is no issue with non-ASCII printing if guacamole published at the
root of tomcat server (i.e. 192.168.1.9:8080/ istead
192.168.1.9:8080/guacamole
I just deleted all content of webapp folder and renamed guacamole.war to
ROOT.war
пт, 6 янв. 2023 г. в 20:48, Евгений Н. Жуков <eu...@gmail.com>:
> Did some experiments, printing works fine with apache & IIS but not
> working with nginx.
>
> пт, 6 янв. 2023 г. в 02:27, Евгений Н. Жуков <eu...@gmail.com>:
>
>> URIencode already set to UTF-8, printing with no proxy works fine, also
>> works with apache, but still not working with nginx
>>
>> пт, 6 янв. 2023 г. в 02:23, Michael Jumper <mj...@apache.org>:
>>
>>> On Thu, Jan 5, 2023 at 3:13 PM Евгений Н. Жуков <eu...@gmail.com>
>>> wrote:
>>>
>>>> Hi! Using 1.4 with nginx configured like
>>>> https://guacamole.apache.org/doc/gug/reverse-proxy.html
>>>> faced with issue printing when the job has Russian characters. The web
>>>> session stops working, catalina.out contain following error:
>>>>
>>>> Invalid character found in the request target
>>>> [/guacamole/api/session/tunnels/420842f2-118b-42e6-8118-eb2144da6a32/streams/0/<C8D2D1209620C1EBEEEAEDEEF2>.pdf?token=E8ACB2365B3E87D63B487F17F198A16BF52D67E4F32A2EC87A5A52B8F5BA21FC
>>>> ]. The valid characters are defined in RFC 7230 and RFC 3986
>>>>
>>>> How to fix nginx config to correctly print from guacamole?
>>>>
>>>
>>> Not Nginx, but Tomcat. You need to configure Tomcat to accept UTF-8
>>> characters in the URIs of requests:
>>>
>>>
>>> https://guacamole.apache.org/doc/gug/reverse-proxy.html#preparing-your-servlet-container
>>>
>>> From above:
>>>
>>> "Be sure to specify the URIEncoding="UTF-8" attribute as above to ensure
>>> that connection names, user names, etc. are properly received by the web
>>> application. If you will be creating connections that have Cyrillic,
>>> Chinese, Japanese, or other non-Latin characters in their names or
>>> parameter values, this attribute is required."
>>>
>>> - Mike
>>>
>>>
>>
>> --
>> Евгений Жуков
>> +79534155676 skype: xrt_nn
>>
>
>
> --
> Евгений Жуков
> +79534155676 skype: xrt_nn
>
--
Евгений Жуков
+79534155676 skype: xrt_nn
Re: Printing job with non-ASCII name thru nginx
Posted by "Евгений Н. Жуков" <eu...@gmail.com>.
Did some experiments, printing works fine with apache & IIS but not working
with nginx.
пт, 6 янв. 2023 г. в 02:27, Евгений Н. Жуков <eu...@gmail.com>:
> URIencode already set to UTF-8, printing with no proxy works fine, also
> works with apache, but still not working with nginx
>
> пт, 6 янв. 2023 г. в 02:23, Michael Jumper <mj...@apache.org>:
>
>> On Thu, Jan 5, 2023 at 3:13 PM Евгений Н. Жуков <eu...@gmail.com>
>> wrote:
>>
>>> Hi! Using 1.4 with nginx configured like
>>> https://guacamole.apache.org/doc/gug/reverse-proxy.html
>>> faced with issue printing when the job has Russian characters. The web
>>> session stops working, catalina.out contain following error:
>>>
>>> Invalid character found in the request target
>>> [/guacamole/api/session/tunnels/420842f2-118b-42e6-8118-eb2144da6a32/streams/0/<C8D2D1209620C1EBEEEAEDEEF2>.pdf?token=E8ACB2365B3E87D63B487F17F198A16BF52D67E4F32A2EC87A5A52B8F5BA21FC
>>> ]. The valid characters are defined in RFC 7230 and RFC 3986
>>>
>>> How to fix nginx config to correctly print from guacamole?
>>>
>>
>> Not Nginx, but Tomcat. You need to configure Tomcat to accept UTF-8
>> characters in the URIs of requests:
>>
>>
>> https://guacamole.apache.org/doc/gug/reverse-proxy.html#preparing-your-servlet-container
>>
>> From above:
>>
>> "Be sure to specify the URIEncoding="UTF-8" attribute as above to ensure
>> that connection names, user names, etc. are properly received by the web
>> application. If you will be creating connections that have Cyrillic,
>> Chinese, Japanese, or other non-Latin characters in their names or
>> parameter values, this attribute is required."
>>
>> - Mike
>>
>>
>
> --
> Евгений Жуков
> +79534155676 skype: xrt_nn
>
--
Евгений Жуков
+79534155676 skype: xrt_nn
Re: Printing job with non-ASCII name thru nginx
Posted by "Евгений Н. Жуков" <eu...@gmail.com>.
URIencode already set to UTF-8, printing with no proxy works fine, also
works with apache, but still not working with nginx
пт, 6 янв. 2023 г. в 02:23, Michael Jumper <mj...@apache.org>:
> On Thu, Jan 5, 2023 at 3:13 PM Евгений Н. Жуков <eu...@gmail.com>
> wrote:
>
>> Hi! Using 1.4 with nginx configured like
>> https://guacamole.apache.org/doc/gug/reverse-proxy.html
>> faced with issue printing when the job has Russian characters. The web
>> session stops working, catalina.out contain following error:
>>
>> Invalid character found in the request target
>> [/guacamole/api/session/tunnels/420842f2-118b-42e6-8118-eb2144da6a32/streams/0/<C8D2D1209620C1EBEEEAEDEEF2>.pdf?token=E8ACB2365B3E87D63B487F17F198A16BF52D67E4F32A2EC87A5A52B8F5BA21FC
>> ]. The valid characters are defined in RFC 7230 and RFC 3986
>>
>> How to fix nginx config to correctly print from guacamole?
>>
>
> Not Nginx, but Tomcat. You need to configure Tomcat to accept UTF-8
> characters in the URIs of requests:
>
>
> https://guacamole.apache.org/doc/gug/reverse-proxy.html#preparing-your-servlet-container
>
> From above:
>
> "Be sure to specify the URIEncoding="UTF-8" attribute as above to ensure
> that connection names, user names, etc. are properly received by the web
> application. If you will be creating connections that have Cyrillic,
> Chinese, Japanese, or other non-Latin characters in their names or
> parameter values, this attribute is required."
>
> - Mike
>
>
--
Евгений Жуков
+79534155676 skype: xrt_nn
Re: Printing job with non-ASCII name thru nginx
Posted by Michael Jumper <mj...@apache.org>.
On Thu, Jan 5, 2023 at 3:13 PM Евгений Н. Жуков <eu...@gmail.com>
wrote:
> Hi! Using 1.4 with nginx configured like
> https://guacamole.apache.org/doc/gug/reverse-proxy.html
> faced with issue printing when the job has Russian characters. The web
> session stops working, catalina.out contain following error:
>
> Invalid character found in the request target
> [/guacamole/api/session/tunnels/420842f2-118b-42e6-8118-eb2144da6a32/streams/0/<C8D2D1209620C1EBEEEAEDEEF2>.pdf?token=E8ACB2365B3E87D63B487F17F198A16BF52D67E4F32A2EC87A5A52B8F5BA21FC
> ]. The valid characters are defined in RFC 7230 and RFC 3986
>
> How to fix nginx config to correctly print from guacamole?
>
Not Nginx, but Tomcat. You need to configure Tomcat to accept UTF-8
characters in the URIs of requests:
https://guacamole.apache.org/doc/gug/reverse-proxy.html#preparing-your-servlet-container
From above:
"Be sure to specify the URIEncoding="UTF-8" attribute as above to ensure
that connection names, user names, etc. are properly received by the web
application. If you will be creating connections that have Cyrillic,
Chinese, Japanese, or other non-Latin characters in their names or
parameter values, this attribute is required."
- Mike