Skip to content

MSC4330: specify HTTP and TLS versions which must be supported #4330

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

MSC4330: specify HTTP and TLS versions which must be supported #4330

wants to merge 1 commit into from
+27 −0

Conversation

famfo
Copy link

@famfo famfo commented Aug 17, 2025

@turt2live turt2live added proposal A matrix spec change proposal s2s Server-to-Server API (federation) client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Aug 18, 2025
turt2live
turt2live reviewed Aug 18, 2025
View reviewed changes
proposals/4330-specify-http-versions.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation requirements:

  • Server (Client-Server API)
  • Server (Federation API)
  • Identity Server
  • Push Gateway
  • Application Service
  • Client

For the above, evidence that a majority of existing implementations support the HTTP/2 protocol may be required. Currently Synapse, for example, appears to send out HTTP/1.1 requests.

@richvdh
Copy link
Member

richvdh commented Aug 18, 2025

Related: matrix-org/matrix-spec#696, matrix-org/matrix-spec#1666

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@turt2live turt2live turt2live left review comments

Assignees
No one assigned
Labels
application services client-server Client-Server API identity service kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal push s2s Server-to-Server API (federation)
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@famfo @richvdh @turt2live