Re: HTTPS Invalid character found in method name. HTTP method names must be tokens.

2019-03-19 Thread Jan Vomlel
Java 10 - OK Java 11 Oracle or Adopt - Fail Chrome, Edge - OK Firefox 60, Internet explorer 11 - Fail Server is in our test environment on Linux. When I tryed to reproduce this bug on my computer (Windows 10), bug did not occure. On our test environment it occures irregularly, a few tests

Re: HTTPS Invalid character found in method name. HTTP method names must be tokens.

2019-03-19 Thread Mark Thomas
Thanks for all that data. Very strange. It is as if the server picks the wrong key to decrypt with. Given you can reproduce this, I suggest trying different versions of Java on the server to see if you can determine a pattern. Also, if you are able to provide a test case that reliably

Re: HTTPS Invalid character found in method name. HTTP method names must be tokens.

2019-03-19 Thread Jan Vomlel
Hello Mark, communication is on https://drive.google.com/open?id=12ZqbgKkHzGKzXk19ssIcJMX6iQBUE4fQ file 18-03-2019-3-filtered-one-connection.pcapng There is also full communication log from wireshark and catalina.out. Critical packet contains data: 17 03 03 01 AB 00 00 00   00 00 00 00 01

Re: HTTPS Invalid character found in method name. HTTP method names must be tokens.

2019-03-18 Thread Mark Thomas
On 18/03/2019 10:49, Jan Vomlel wrote: Thank you Mark. I enabled the logger org.apache.coyote.http11. I cannot paste line org.apache.coyote.http11.Http11InputBuffer.parseRequestLine here, because it contains not printable characters and copy paste doesnot work. It seems like bug in tomcat

Re: HTTPS Invalid character found in method name. HTTP method names must be tokens.

2019-03-18 Thread Jan Vomlel
Thank you Mark. I enabled the logger org.apache.coyote.http11. I cannot paste line org.apache.coyote.http11.Http11InputBuffer.parseRequestLine here, because it contains not printable characters and copy paste doesnot work. It seems like bug in tomcat or jdk.   ??? Log contains now:

Re: HTTPS Invalid character found in method name. HTTP method names must be tokens.

2019-03-14 Thread Mark Thomas
On 13/03/2019 14:41, Jan Vomlel wrote: > We use selenium for our application testing. Our tests sometime fail > with message "Invalid character found in method name" Error occures > only on https and on on firefox 60 and internet explorer 11. Chrome, > edge is OK. > > We use Tomcat 9.0.16,

HTTPS Invalid character found in method name. HTTP method names must be tokens.

2019-03-13 Thread Jan Vomlel
We use selenium for our application testing. Our tests sometime fail with message "Invalid character found in method name" Error occures only on https and on on firefox 60 and internet explorer 11. Chrome, edge is OK. We use Tomcat 9.0.16, Java 11 (Adopt Open JDK 11.0.2+9) on Linux,