Re: AccessLogValve and IPv6 string representation (RFC 5952 section 4)

Nevermind. For some reason we had omitted this is already supported by the ipv6Canonical flag. RTFM! Manuel Dominguez Sarmiento > On 13 Apr 2020, at 20:46, Manuel Dominguez Sarmiento wrote: > >  Hi, we are in the middle of a thorough review to fully support IPv6 across > our platform. It

Re: AccessLogValve and IPv6 string representation (RFC 5952 section 4)

Am 2020-04-14 um 01:45 schrieb Manuel Dominguez Sarmiento: Hi, we are in the middle of a thorough review to fully support IPv6 across our platform. It has come to our attention that Java does not fully conform to RFC 5952 section 4 which deals with IPv6 zero compression (i.e. ::1 instead of

AccessLogValve and IPv6 string representation (RFC 5952 section 4)

Hi, we are in the middle of a thorough review to fully support IPv6 across our platform. It has come to our attention that Java does not fully conform to RFC 5952 section 4 which deals with IPv6 zero compression (i.e. ::1 instead of 0:0:0:0:0:0:0:1 for localhost). We have confirmed that

Re: Tomcat SSL Connector - Http11NioProtocol - javax.crypto.ShortBufferException on second request

On Mon, Apr 13, 2020 at 7:07 PM Mark Thomas wrote: > On 13/04/2020 11:39, Parigino Andrea Aiello wrote: > > Hello! > > i'm having a problem with Tomcat 8.5.51 hosting my Spring Boot 2 > > application (with 2-way SSL); > > The first thing to do is to update to 8.5.54 and re-test. > Also test

Re: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

Thanks Mark. Including the request line (encoded if necessary to avoid issues with control characters) should definitely help. Getting through all the way to AccessLogValve would also help, but the most important bit is improving the error message. *Manuel Dominguez Sarmiento* On 13/04/2020

RE: Alternatives for AJP

https://nvd.nist.gov/vuln/detail/CVE-2020-1938 -Original Message- From: stephane passignat Sent: Sunday, April 12, 2020 4:00 AM To: Tomcat Users List Subject: Re: Alternatives for AJP Hi Which vulnerability are you mentioning ? Thanks ⁣Envoyé par BlueMail ​ Le 10 avr. 2020 à 17:45,

Re: Tomcat SSL Connector - Http11NioProtocol - javax.crypto.ShortBufferException on second request

On 13/04/2020 11:39, Parigino Andrea Aiello wrote: > Hello! > i'm having a problem with Tomcat 8.5.51 hosting my Spring Boot 2 > application (with 2-way SSL); The first thing to do is to update to 8.5.54 and re-test. Mark > In short is an application with both server and client SOAP interfaces

Re: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

On 13/04/2020 17:25, Manuel Dominguez Sarmiento wrote: > Hi, we're reviewing our logs, are we are ocasionally getting the > following stack traces: > > 09-Apr-2020 11:29:19.489 INFO [tomcat-http-81] > org.apache.coyote.http11.Http11Processor.service Error parsing HTTP > request header >  Note:

java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

Hi, we're reviewing our logs, are we are ocasionally getting the following stack traces: 09-Apr-2020 11:29:19.489 INFO [tomcat-http-81] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header  Note: further occurrences of HTTP request parsing errors will be logged

Re: java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

Sorry, I was not aware of that behaviour even when changing the subject. I'll send a new, separate, unrelated message. * Manuel Dominguez Sarmiento* On 12/04/2020 16:08, Mark Thomas wrote: Please don't hijack an existing thread. Start a new message for a new topic. (Replying to an existing

Tomcat SSL Connector - Http11NioProtocol - javax.crypto.ShortBufferException on second request

Hello! i'm having a problem with Tomcat 8.5.51 hosting my Spring Boot 2 application (with 2-way SSL); In short is an application with both server and client SOAP interfaces (first called as server, then it act as client). The problem: on first request (sent by SoapUI or other external client)