Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide better control over which HTTP protocols are enabled #1668

Closed
wants to merge 2 commits into from

Conversation

essen
Copy link
Member

@essen essen commented Feb 10, 2025

Over cleartext TCP the protocols option lists the enabled protocols. The default is to allow both HTTP/1.1 and HTTP/2.

Over TLS the default protocol to use when ALPN is not used can now be configured via the alpn_default_protocol option.

Performing an HTTP/1.1 upgrade to HTTP/2 over TLS is now rejected with an error as connecting to HTTP/2 over TLS requires the use of ALPN (or that HTTP/2 be the default when connecting over TLS).

Over cleartext TCP the `protocols` option lists the enabled
protocols. The default is to allow both HTTP/1.1 and HTTP/2.

Over TLS the default protocol to use when ALPN is not used
can now be configured via the `alpn_default_protocol` option.

Performing an HTTP/1.1 upgrade to HTTP/2 over TLS is now
rejected with an error as connecting to HTTP/2 over TLS
requires the use of ALPN (or that HTTP/2 be the default
when connecting over TLS).
To avoid intermittent errors that are more likely as more
tests are calling cowboy:stop_listener.
@essen essen closed this Feb 10, 2025
@essen essen deleted the better-control-over-protocol branch February 10, 2025 16:17
@essen
Copy link
Member Author

essen commented Feb 10, 2025

Merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant