Re: [jetty-users] No no_application_protocol when server doesn't support any client protocol

2019-11-13 Thread Simone Bordet
Hi, On Wed, Nov 13, 2019 at 2:32 PM Glen Peterson wrote: > > 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. No need to apologize! This is the Jetty community

Re: [jetty-users] No no_application_protocol when server doesn't support any client protocol

2019-11-12 Thread John Jiang
Anyway, just filed https://github.com/eclipse/jetty.project/issues/4305 On Tue, Nov 12, 2019 at 2:48 PM John Jiang wrote: > Hi, > Using 9.4.22. > > My jetty server supports HTTP/2, including h2c and h2, and try the below > command, > openssl s_client -alpn h3,h4 -connect host:port > For this

Re: [jetty-users] No no_application_protocol when server doesn't support any client protocol

2019-11-12 Thread Glen Peterson
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 ---

[jetty-users] No no_application_protocol when server doesn't support any client protocol

2019-11-11 Thread John Jiang
Hi, Using 9.4.22. My jetty server supports HTTP/2, including h2c and h2, and try the below command, openssl s_client -alpn h3,h4 -connect host:port For this case, per RFC 7301 section 3.2, the server shall alter fatal no_application_protocol. But with my testing, the server raised warning