jamesnetherton commented on issue #7894: URL: https://github.com/apache/camel-quarkus/issues/7894#issuecomment-3472060649
This seems to be due to a change in behaviour in the response from the JDK HTTP server. Before JDK 25, if you send an HTTP request to an HTTPS endpoint, the connection gets closed. With JDK 25, some data is written to the client before connection closure like: ``` [0x15][0x3][0x3][0x0][0x2][0x2][0x50][\r][\n] ``` Which is probably the [TLS closure alert](https://datatracker.ietf.org/doc/html/rfc5246#section-7.2). 50 = `decode_error`. `DefaultHttpResponseParser` in the Apache HTTP client tries to parse that data, but can't, so you get `ClientProtocolException`, instead of the expected `NoHttpResponseException`. The simplest way to handle it in the test is to expect either exception. All we want to verify is that you can't send a plain HTTP request to a Jolokia endpoint secured with SSL / TLS. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
