Did some experiments, printing works fine with apache & IIS but not working with nginx.
пт, 6 янв. 2023 г. в 02:27, Евгений Н. Жуков <[email protected]>: > 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 <[email protected]>: > >> On Thu, Jan 5, 2023 at 3:13 PM Евгений Н. Жуков <[email protected]> >> 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
