Cloudflare now returns structured Markdown responses for Cloudflare-generated 1xxx errors when clients send Accept: text/markdown.
Each response includes YAML frontmatter plus guidance sections (What happened / What you should do) so agents can make deterministic retry and escalation decisions without parsing HTML.
In measured 1,015 comparisons, Markdown reduced payload size and token footprint by over 98% versus HTML.
Included frontmatter fields:
error_code,error_name,error_category,http_statusray_id,timestamp,zonecloudflare_error,retryable,retry_after(when applicable),owner_action_required
Default behavior is unchanged: clients that do not explicitly request Markdown continue to receive HTML error pages.
Negotiation behavior
Cloudflare uses standard HTTP content negotiation on the Accept header.
Accept: text/markdown-> MarkdownAccept: text/markdown, text/html;q=0.9-> MarkdownAccept: text/*-> MarkdownAccept: */*-> HTML (default browser behavior)
When multiple values are present, Cloudflare selects the highest-priority supported media type using q values. If Markdown is not explicitly preferred, HTML is returned.
Availability
Available now for Cloudflare-generated 1xxx errors.
Get started
curl -H "Accept: text/markdown" https://<your-domain>/cdn-cgi/error/1015Reference: Cloudflare 1xxx error documentation
Source: Cloudflare
Latest Posts
- MC1455035: Power Pages Rolls Out Early Upgrade to Version 9.8.8.5 with Performance and Security Fixes

- MC1455050: Power Platform Adds GitHub Support for Source Code Integration with Enhanced APIs and Performance

- MC1455051: Dynamics 365 Customer Service and Contact Center Adds Workforce Alerts for Intraday Volume Spikes

- Workers, Access – You can now enable Access on a Worker or all Workers at once







