DDoS protection and Cloudflare cache

Hello, all!
Has anyone connected their dating site to cloudflare (to prevent potential DDoS attacks)?
The specificity of the dating site is such that caching by the cloudflare service will interfere with users. For example, because the same URL shows different content depending on whether the user is logged in (or their status).
To completely disable caching on cloudflare, I followed the instructions:
“Create a page rule that matches your entire domain ( *domain.com/* ) by setting the Cache Level to Bypass and then clear the cache.”(с)
Now almost all content is downloaded in transit through cloudflare from my server. But some of the content is still loaded from the cloudflare cache. It confuses me. What can be wrong? Can anyone suggest how to solve this?

Regarding cache and the graph you provided, that is “normal” if you have traffic on your Website.
One color is the cache, while the other is traffic/requests going directly to your origin server (files were not being cached, either the “Dynamic content”).

Traffic neccesarly does not mean you are actually under a DDoS attack, while having the “bypass” option, meaning all the requests are going directly to your server/host and no content is being “in cache” at Cloudflare edge (network).

Kindly, see below articles:

Thanks)
I followed the instruction: “Create a page rule that matches your entire domain (*domain.com/*) by setting the Cache Level to Bypass and then clear the cache.”(с)
I don’t understand where does cloudflare cache come from?
Cloudflare is ignoring the rule and caching something?

Can anyone please give me an explanation?

If you set Bypass, Cloudflare will not cache a standard CSS, JS, images, etc. supported MIME file types.
Meaning, all the requests will go straight to your origin host/server.

You are having issue with content being cached and served to your visitors?
If so, do not use “Cache Everything”, rather use “Cache Standard” in that case.

Regarding the DDoS, I’ve already written in my previous post.

Again, may I ask what are you trying to achieve?

In short, from the closest possible and available location (server) to the visitor.

May I ask how did you checked that and are you sure about it?
Do you see the BYPASS, HIT, MISS, or some other value in the HTTP header as a response for a single file?

I followed the instructions about which I already wrote earlier. I disabled caching (Bypass).
The graph shows the availability of cached responses to users. Is this graph broken? Here’s what I want to know. Just look at my screenshot, you can see that the graph shows the presence of cached responses to users.

Cloudflare will still cache a number of http(s) response codes unless explicitly directed not to with cache directives from the origin. I work with a number of dating sites, most of whom use a reasonable amount of caching from Cloudflare. Probably worth having your dev team look to improve their app design if you have to disable Cloudflare’s caching ability to access the app.

2 Likes

Hi! Sorry for the delay, I was leaving on a business trip.
Thanks for your reply!
Can you please tell me what responses Cloudflare caches if Bypass is enabled? I thought Bypass turns off caching completely.