All parts of the download URL should be correctly encoded:

https://github.com/apache/guacamole-client/blob/0.9.14/guacamole/src/main/webapp/app/rest/services/tunnelService.js#L192-L198

Are you able to grab the HTTP request that's failing (ie: from the Tomcat
access logs)? It should be a GET request with "api/session/tunnels/" and
"/streams/" within the path.

Is there any sort of proxy between your browser and Tomcat which might be
handling the request incorrectly?

- Mike


On Thu, Feb 22, 2018 at 12:04 PM, Евгений Н. Жуков <eugene.zhu...@gmail.com>
wrote:

> I found error out catalina.out during printing nonASCII job
>
> Feb 22, 2018 11:02:02 PM org.apache.coyote.http11.AbstractHttp11Processor
> process
> INFO: Error parsing HTTP request header
>  Note: further occurrences of HTTP header parsing errors will be logged at
> DEBUG level.
> java.lang.IllegalArgumentException: Invalid character found in the
> request target. The valid characters are defined in RFC 7230 and RFC 3986
>         at org.apache.coyote.http11.InternalInputBuffer.parseRequestLine(
> InternalInputBuffer.java:189)
>         at org.apache.coyote.http11.AbstractHttp11Processor.process(
> AbstractHttp11Processor.java:1028)
>         at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.
> process(AbstractProtocol.java:637)
>         at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.
> run(JIoEndpoint.java:316)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
>         at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(
> TaskThread.java:61)
>         at java.lang.Thread.run(Thread.java:748)
>
>
> 2018-02-22 22:51 GMT+03:00 Евгений Н. Жуков <eugene.zhu...@gmail.com>:
>
>> Just inzip an old vm with debian & 0.9.10 , in this version printing with
>> nonASCII job name works fine.
>>
>> 2018-02-22 22:49 GMT+03:00 Евгений Н. Жуков <eugene.zhu...@gmail.com>:
>>
>>> This issue from 0.9.12.
>>> In server.xml uriencoding already set to UTF8
>>>
>>>
>>>
>>>
>>> 2018-02-22 22:43 GMT+03:00 Mike Jumper <mike.jum...@guac-dev.org>:
>>>
>>>> Assuming you are using Tomcat, please verify that the following is set
>>>> on the applicable connector in your server.xml:
>>>>
>>>>     URIEncoding="UTF-8"
>>>>
>>>> See:
>>>>
>>>> https://wiki.apache.org/tomcat/FAQ/CharacterEncoding#Q8
>>>>
>>>> - Mike
>>>>
>>>>
>>>> On Feb 22, 2018 11:35, "Евгений Н. Жуков" <eugene.zhu...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi, just installed latest version, and got old problem. If printing
>>>>> job has non-ASCII symbols (for example russians characters) the job stucks
>>>>> in printing queue, or I getting empty pdf file.
>>>>>
>>>>>
>>>>> --
>>>>> Евгений Жуков
>>>>> +79534155676 <+7%20953%20415-56-76>  skype: xrt_nn
>>>>>
>>>>
>>>
>>>
>>> --
>>> Евгений Жуков
>>> +79534155676 <+7%20953%20415-56-76>  skype: xrt_nn
>>>
>>
>>
>>
>> --
>> Евгений Жуков
>> +79534155676 <+7%20953%20415-56-76>  skype: xrt_nn
>>
>
>
>
> --
> Евгений Жуков
> +79534155676 <+7%20953%20415-56-76>  skype: xrt_nn
>

Reply via email to