Can you actually customize that Cloudflare error page? I thought that was their error page when they lose connection with your site and custom error pages was just the ones your app creates, like 404, 403, etc?
I think the intent is for joke pages, like the demo link which acts like error 500 saying the host is on fire etc but really serves as 200 OK, not your actual Cloudflare service errors.
> Error Pages do not apply to responses with an HTTP status code of 500, 501, 503, or 505. These exceptions help avoid issues with specific API endpoints and other web applications. You can still customize responses for these status codes using Custom Error Rules.
I've been thinking about returning a fake error page instead of the "you are banned" or "you country has been blocked".
Well, that's one way to show contempt for your users.
What is this for? I feel like that is missing from the faq. I would say it's a joke, but it looks too serious for that.
Speaking of which, I made this some years ago: https://www.brainonfire.net/rx/the-joke.png
If your site goes down people can assume it’s cloudflare’s fault. You can blend in with the crowd without actually using CF.
that's what makes it funnier
Can you actually customize that Cloudflare error page? I thought that was their error page when they lose connection with your site and custom error pages was just the ones your app creates, like 404, 403, etc?
I think the intent is for joke pages, like the demo link which acts like error 500 saying the host is on fire etc but really serves as 200 OK, not your actual Cloudflare service errors.
You can, on the $30 plan - you can give it a hidden url on your current domain and it will cache & serve that content.
On free plans you can't, on business/enterprise plans you can.
Edit: Gemini says you could make a custom worker and do a 5XX redirect that way, but I haven't tried it. Does make sense though.
This works for errors at the origin or in a Worker, but won't for errors at the edge, because those are in front of Workers.
I think Gemini refers to Web Workers API rather than a Cloudflare Worker. And that should work indeed.
the custom error page is configurable at a domain (zone) level
which sometimes gets annoying because branding for subdomains could be different.
https://developers.cloudflare.com/rules/custom-errors/edit-e...
> Error Pages do not apply to responses with an HTTP status code of 500, 501, 503, or 505. These exceptions help avoid issues with specific API endpoints and other web applications. You can still customize responses for these status codes using Custom Error Rules.
From that page ;)
It should spew random garbage at the bottom of the page periodically to mimic Cloudbleed.