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 pa

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 demonst

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 19

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 or

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

2019-03-18 Thread Jan Vomlel
that 566 characters. ] 15-Mar-2019 16:28:59.288 INFO [https-jsse-nio-8444-exec-7] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header  Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.  java.lang.IllegalArgumentExceptio

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

2019-03-14 Thread Mark Thomas
ps-jsse-nio-8444-exec-6|2019-02-27 > 18:03:16.327 CET|Finished.java:581|Consuming client Finished handshake > message ( > "Finished": { >   "verify data": { >     0000: 0C 1D 2A A3 97 60 B3 E4   72 E3 31 10 >   }'} > ) > 27-

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

2019-03-13 Thread Jan Vomlel
t header  Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.  java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens     at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:414

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

2019-02-07 Thread Sean Dawson
level. > > java.lang.IllegalArgumentException: Invalid character found in > > method name. HTTP method names must be tokens at > > org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(Abstr > actNioInputBuffer.java:232) > > > > I can provide the full s

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

2019-02-07 Thread Christopher Schultz
p11Processor.process 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 > method name. HTTP method names must be token

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

2019-02-07 Thread Mark Thomas
der > Note: further occurrences of HTTP header parsing errors will be logged at > DEBUG level. > java.lang.IllegalArgumentException: Invalid character found in method > name. HTTP method names must be tokens > at > org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(A

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

2019-02-07 Thread Sean Dawson
ogged at DEBUG level. java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:232) I can provide the full stack trace if needed. But we've