You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting to a HTTPS server built with actix-web, TLS-ALPN fails to work properly, and HTTP/1.1 is used instead of HTTP/2.
The documentation says that "actix-web automatically upgrades connections to HTTP/2.0 if possible", but it appears that it's not being upgraded properly.
I think we should give the utmost attention to this issue since one of the biggest selling points of actix-web plain doesn't work anymore.
Currently trying to pinpoint the faulty version that caused the regression
Edit: Found.
Actix-web 0.7.3:
starting benchmark...
spawning thread #0: 100 total client(s). 1000 total requests
TLS Protocol: TLSv1.2
Cipher: ECDHE-RSA-AES128-GCM-SHA256
Server Temp Key: ECDH P-256 256 bits
Application protocol: h2
Actix 0.7.4 and above:
starting benchmark...
spawning thread #0: 100 total client(s). 1000 total requests
TLS Protocol: TLSv1.2
Cipher: ECDHE-RSA-AES128-GCM-SHA256
Server Temp Key: ECDH P-256 256 bits
No protocol negotiated. Fallback behaviour may be activated
Server does not support NPN/ALPN. Falling back to HTTP/1.1.
Application protocol: http/1.1
When connecting to a HTTPS server built with actix-web, TLS-ALPN fails to work properly, and HTTP/1.1 is used instead of HTTP/2.
The documentation says that "actix-web automatically upgrades connections to HTTP/2.0 if possible", but it appears that it's not being upgraded properly.
Here's a simple example server to show the issue:
And, here's the output when I attempt to connect to it through curl (truncated):
The text was updated successfully, but these errors were encountered: