Rules - More flexible fallback handling — Custom Errors now support fetching assets returned with 4xx or 5xx status codes
1y ago
Source
CloudflareRules - More flexible fallback handling — Custom Errors now support fetching assets returned with 4xx or 5xx status codescloudflare.comCustom Errors can now fetch and store assets and error pages from your origin even if they are served with a 4xx or 5xx HTTP status code — previously, only 200 OK responses were allowed. What’s new: You can now upload error pages and error assets that return error status codes (for example, 403, 500, 502, 503, 504) when fetched. These assets are stored and minified at the edge, so they can be reused across multiple Custom Error rules without triggering requests to the origin. This is especially useful for retrieving error content or downtime banners from your backend when you can’t override the origin status code. Learn more in the Custom Errors documentation.
You might also wanna read
Elevated errors for Responses API
OpenAI
Custom Cloudflare-Style Error Page Generator: Open-Source Tool for Website Error Pages
This article describes an open-source GitHub project called 'cloudflare-error-page' that allows users to create customized error pages mimic
github.com·6mo agoElevated 401 errors for API endpoints
OpenAI
Implementing Custom Error Types in Rust for Cleaner Axum Web Application Error Handling
This article provides a practical guide for Rust developers on implementing custom error types to simplify error handling in Axum web applic
rup12.net·7mo ago
Centralizing Error Handling in Rust with Custom AppError Enums
This article discusses the importance of centralizing error handling in Rust applications using a custom AppError enum combined with map_err
tristonarmstrong.com·1mo ago
Elevated error rate for Responses API
OpenAI
Comments
Sign in to join the conversation.
No comments yet. Be the first.