[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] No no_application_protocol when server doesn't support any client protocol
|
I saw HTTP/2 and thought it might be related to some stuff I had worked on. I guess I effectively posted a promotion for my test project, which I should not do. I apologize.
My test project does not support h3. I don't even know what h3 is. Or h4 or h2c for that matter. Maybe that's why I was so quick to gloss over that part.
Glen,
On Tue, Nov 12, 2019 at 6:19 PM Glen Peterson <glen.k.peterson@xxxxxxxxx> wrote:
>
> Hi John,
>
> I was having similar issues and made a minimal sample project to debug my issues. When I run it and issue:
> $ openssl s_client -alpn h3,h4 -connect localhost:8443
> in another terminal, I get:
>
> ...
> Peer signing digest: SHA256
> Peer signature type: ECDSA
> Server Temp Key: X25519, 253 bits
> ---
> SSL handshake has read 872 bytes and written 403 bytes
> Verification error: self signed certificate
> ---
> New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
> Server public key is 256 bit
> Secure Renegotiation IS NOT supported
> Compression: NONE
> Expansion: NONE
> ALPN protocol: h3
> Early data was not sent
> Verify return code: 18 (self signed certificate)
> ---
> read:errno=0
How did you support h3?
--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
--
Glen K. Peterson
(828) 393-0081
