Skip to content

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

Open
famfo wants to merge 1 commit into
matrix-org:mainfrom
famfo:http-tls-version
Open

famfo wants to merge 1 commit into
matrix-org:mainfrom
famfo:http-tls-version

Conversation

@famfo

@famfo famfo commented Aug 17, 2025

Copy link
Copy Markdown

@turt2live turt2live added proposal A matrix spec change proposal. Process state. A-Federation Server-to-Server API (federation) A-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

Copy link
Copy Markdown
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

richvdh commented Aug 18, 2025

Copy link
Copy Markdown
Member

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

Labels

A-Application Services Relates to the appservices spec A-Client Server Client-Server API A-Federation Server-to-Server API (federation) A-Identity Service A-Push 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. Process state.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants