From 8a9c5c8f4644952aebd625ccdfa31fa92fcb5ccd Mon Sep 17 00:00:00 2001 From: Henning Perl Date: Wed, 1 Jul 2026 10:49:43 +0200 Subject: [PATCH 1/2] docs: recommend HTTP/2 for HTTP event sinks 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) --- docs/actions/live-events.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/actions/live-events.mdx b/docs/actions/live-events.mdx index d4312a59a0..782bf1fa92 100644 --- a/docs/actions/live-events.mdx +++ b/docs/actions/live-events.mdx @@ -244,6 +244,9 @@ Unencrypted HTTP endpoints are not supported. Your endpoint must be able to hand with a 2xx status code to acknowledge successful processing of the event. HTTP redirects are _not_ followed and are treated as delivery failures. +We strongly recommend that your endpoint supports HTTP/2. HTTP/2 multiplexing lets Ory deliver many events concurrently over a +single connection, resulting in significantly more efficient throughput for event delivery. + Authentication is possible by including credentials in the URL (HTTP Basic Authentication), for example: `https://username:password@example/com/my-event-endpoint` From b64920efee9bbdbf0ab1bf365fc6f178f203b747 Mon Sep 17 00:00:00 2001 From: Henning Perl Date: Wed, 1 Jul 2026 11:57:42 +0200 Subject: [PATCH 2/2] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- docs/actions/live-events.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/actions/live-events.mdx b/docs/actions/live-events.mdx index 782bf1fa92..ea7dc00f8f 100644 --- a/docs/actions/live-events.mdx +++ b/docs/actions/live-events.mdx @@ -249,7 +249,7 @@ single connection, resulting in significantly more efficient throughput for even Authentication is possible by including credentials in the URL (HTTP Basic Authentication), for example: -`https://username:password@example/com/my-event-endpoint` +`https://username:password@example.com/my-event-endpoint` ### Stream to AWS SNS