10000 OpenSSL defaults to http1.1 · Issue #27 · openssl-net/openssl-net · GitHub
[go: up one dir, main page]
Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

OpenSSL defaults to http1.1 #27

Open
rforbes opened this issue Aug 13, 2015 · 3 comments
Open

OpenSSL defaults to http1.1 #27

rforbes opened this issue Aug 13, 2015 · 3 comments

Comments

@rforbes
Copy link
rforbes commented Aug 13, 2015

I am setting up a new ssl tunnel using this library. Everything works great except for the ALPN negotiation. When I use firefox it sends h2-12, SPDY3, and HTTP1.1. I am getting a negotiation with HTTP1.1. If I use openssl with s_client and use the -alpn flag then the server will return h2-12 correctly.

What it looks like is openssl needs some way to specify what ALPN protocol should be negotiated. Using s_server there is a flag -alpn we can specify this. Is it possible to set something like that with this library?
@flaub
Copy link
flaub commented Aug 14, 2015

Yes. I need to add an api to allow users to optionally enable features, like ALPN and SNI.

Sent from my iPhone

On Aug 13, 2015, at 11:38 AM, Raymond Forbes notifications@github.com wrote:

I am setting up a new ssl tunnel using this library. Everything works great except for the ALPN negotiation. When I use firefox it sends h2-12, SPDY3, and HTTP1.1. I am getting a negotiation with HTTP1.1. If I use openssl with s_client and use the -alpn flag then the server will return h2-12 correctly.

What it looks like is openssl needs some way to specify what ALPN protocol should be negotiated. Using s_server there is a flag -alpn we can specify this. Is it possible to set something like that with this library?

—
Reply to this email directly or view it on GitHub.

@rforbes
Copy link
Author
rforbes commented Sep 17, 2015

any idea when this functionality could be added?

thanks!

@vtortola
Copy link

Same issue here :) Calling with Google Chrome and getting HTTP 1.1

@rforbes rforbes mentioned this issue Dec 1, 2015
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@flaub @vtortola @rforbes
0