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 attempting to enable HTTP/2 on a server built using the Loco.rs framework, the server responds with HTTP/1.1
curl -I --http2 http://localhost:5150/_ping
The response indicates HTTP/1.1 instead of HTTP/2.
To Reproduce
Use curl to check the response headers:
curl -I --http2 https://127.0.0.1:3000
The response indicates HTTP/1.1 instead of HTTP/2.
Expected Behavior
The server should respond with HTTP/2 in the response headers when tested using curl or any other HTTP/2 client. This would ensure that the server is properly utilizing HTTP/2, which provides better performance through multiplexing and header compression.
Environment:
Additional Context
How do i configure it in loco?
The text was updated successfully, but these errors were encountered:
Description
When attempting to enable HTTP/2 on a server built using the Loco.rs framework, the server responds with HTTP/1.1
curl -I --http2 http://localhost:5150/_ping
The response indicates HTTP/1.1 instead of HTTP/2.
To Reproduce
Use curl to check the response headers:
curl -I --http2 https://127.0.0.1:3000
The response indicates HTTP/1.1 instead of HTTP/2.
Expected Behavior
The server should respond with HTTP/2 in the response headers when tested using curl or any other HTTP/2 client. This would ensure that the server is properly utilizing HTTP/2, which provides better performance through multiplexing and header compression.
Environment:
Additional Context
How do i configure it in loco?
The text was updated successfully, but these errors were encountered: