guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Евгений Н. Жуков <eugene.zhu...@gmail.com>
Subject Re: printing issues (non-ASCII job name)
Date Thu, 22 Feb 2018 20:39:47 GMT
Yes, tried nginx and apache2

x.x.x.x - - [22/Feb/2018:23:35:16 +0300] "GET
/api/session/tunnels/21ab8066-0e7d-4085-bf26-7ff9fb6aa9f9/streams/0/%3CD2E0E1EBE8F7EDFBE920E4EEEAF3ECE5EDF2%3E.pdf?token=DF441F3D3B8197AC78AD677CC1DFCC5FCE5899FAE829A76F18AE30BEF28CD6C4
HTTP/1.1" 400 5 "https://nr34.com/" "Mozilla/5.0 (Windows NT 10.0; Win64;
x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132
Safari/537.36" "-"


2018-02-22 23:25 GMT+03:00 Mike Jumper <mike.jumper@guac-dev.org>:

> 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.zhukov@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.parseRequestLin
>> e(InternalInputBuffer.java:189)
>>         at org.apache.coyote.http11.AbstractHttp11Processor.process(Abs
>> tractHttp11Processor.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(ThreadPool
>> Executor.java:1142)
>>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.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.zhukov@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.zhukov@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.jumper@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.zhukov@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
>>
>
>


-- 
Евгений Жуков
+79534155676  skype: xrt_nn

Mime
View raw message