From d3047b3d18c6c8c3834de12011f4017cfbf7752a Mon Sep 17 00:00:00 2001 From: Paolo Tagliaferri Date: Fri, 13 Dec 2024 15:10:29 +0000 Subject: [PATCH] Clarify requirements around HTTP endpoint. --- .../docs/logs/get-started/enable-destinations/http.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/docs/logs/get-started/enable-destinations/http.mdx b/src/content/docs/logs/get-started/enable-destinations/http.mdx index d08e4286fd1c994..a6dac762a267d59 100644 --- a/src/content/docs/logs/get-started/enable-destinations/http.mdx +++ b/src/content/docs/logs/get-started/enable-destinations/http.mdx @@ -12,6 +12,10 @@ Cloudflare Logpush now supports the ability to send logs to configurable HTTP en Note that when using Logpush to HTTP endpoints, Cloudflare customers are expected to perform their own authentication of the pushed logs. For example, customers may specify a secret token in the URL or an HTTP header of the Logpush destination. +:::note[Endpoint requirements] +Cloudflare expects that the endpoint is available over HTTPS, using a trusted certificate. The endpoint must accept `POST` requests. +::: + ## Manage via the Cloudflare dashboard