Skip to content

docs: recommend HTTP/2 for HTTP event sinks#2654

Open
hperl wants to merge 4 commits into
masterfrom
event-streams-recommend-http-2
Open

docs: recommend HTTP/2 for HTTP event sinks#2654
hperl wants to merge 4 commits into
masterfrom
event-streams-recommend-http-2

Conversation

@hperl

@hperl hperl commented Jul 1, 2026

Copy link
Copy Markdown
Member

Summary

Adds a strong recommendation to the Live event streams docs that HTTP event sink endpoints support HTTP/2.

HTTP/2 multiplexing lets Ory deliver many events concurrently over a single connection, resulting in significantly more efficient throughput for event delivery.

Changes

  • docs/actions/live-events.mdx — added an HTTP/2 recommendation to the Stream to HTTPS endpoint section, right after the endpoint requirements.

🤖 Generated with Claude Code

Recommend that HTTP event stream endpoints support HTTP/2, since
multiplexing allows for more efficient throughput of event delivery.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 1, 2026 08:49

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the Actions “Live event streams” documentation to recommend using HTTP/2-capable HTTPS endpoints for HTTP event sinks, improving delivery efficiency via multiplexing.

Changes:

  • Adds a strong recommendation that HTTPS event sink endpoints support HTTP/2 to improve concurrent event delivery throughput.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/actions/live-events.mdx Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.

3 participants