Here's the thing, my website is basically protected by a layer of Cloudflare, but the speed of Cloudflare in the country is really a bit strained. It's secure, but the user experience is really poor. In fact, I noticed content related to EdgeOne a long time ago. At first, I didn't plan to get involved because it required posting on X, which I was too lazy to do, so I set it aside until a few days ago when I discovered that EdgeOne offers two free plans without needing to post. Upholding my spirit of "I can do without it, but I can't live without it," I also went to claim two free plans to try out.
EdgeOne free plan claim link: Speed test sharing, unlock more EdgeOne free plans
It requires sharing the speed test results on X and Facebook, but in reality, you just need to click that button; you don't really need to share.
The performance is actually quite good, much faster than before, and this free plan comes with unlimited traffic, though I wonder if it will be cut in the future.
During use, I found that sometimes it still needs to pull data from the origin server (Cloudflare), but going through Cloudflare can be very slow, taking five to six seconds to get the first data. So, I added two new rules based on EdgeOne's WordPress acceleration rules:
- Determine if the user is logged in by checking if the HTTP request header contains wordpress_logged_in_. If not logged in, provide the cached interface; if logged in, do not cache.
- Cache all interfaces ending with / (excluding those after wp-admin).
Today, I noticed in the website backend that a lot of traffic was accessing directly from the origin server, and I didn't want them to access it through Cloudflare's origin server. So, I set up a rule in Cloudflare that requires access to the origin server to go through EdgeOne. I wrote a custom security rule in Cloudflare to check if all traffic accessing the origin server is going through the CDN; if not, block them all.
Let's leave it at that for now. If other issues arise, I'll address them later.