I notice it also doesn't cache my next/image

But I set a rule for that because it has query strings

So I set cloudflare to ignore query strings for next/image

But this still persists, I ideally don't want to setup rules for each page..

Not really a Next.js issue

Are u using the workers platform or the pages platform

Self hosted.

On my own VPS

I mean CF would only be setting Dynamic because something on the response headers is making it questionable so I assume it might be a Next.js issue (?)

It's cloudflare settings the response headers

Not nextjs

U can try cloudflares cache reserve

I think that’s enterprise only

Yeah but the cache control headers are determined by my app

Which would be Next.js

So much of my next app is being dynamically cached which is just stressing my server out. I don’t know if that’s because I have something incorrectly setup or it’s a Next thing

I mean a completely static page with literally one div and some text is being considered “Dynamic” by Cloudflare?? Seems like somethings either broken or I’m doing something wrong

Cloudflare adds headers to the request

nextjs can't know by itself that it's being proxied via cf

Is it a static site or a dynamic site?

Why would CF add cache control headers though

why wouldnt it

if ur vps is being proxied via cloudflare

Cloudflare adds 2-3 headers to it

It says Next.js sets the Cache Control header

Which would make sense

There's 2 different things

Ur local cache (on the vps)

And cf cache

(what cf has cached)

Nextjs can control the local cache

Cloudflare isn't some smarty that it automatically knows by itself what to cache and what to not

I mean it also looks like Next.js appends a bunch of headers

So by default, it forwards all requests to the vps

u gotta manually configure cache rules if u want cloudflare to cache them

For each page?

which can be costly

u can set a wildcard

All requests to this domain should be cached or smthn

Jesus that's gonna be annoying

Is ur project static or dynamic?

More dynamic

But there's multiple static pages

try out appwrite

They'll automatically push ur static assets to a cdn and have the central node server running in a digitalocean container

Well the static assets are cached fine

Theyre still in beta so a lot of stuff is free right now

My only issue is the actual HTML pages

just try having a better hosting

Also have you used tRPC?

Having something over an edge network rather than just one server will pretty much remove any sort of ddos issues

nope

also if u can't move from to any other hosting provider

Setup waf rules to try and block out any of those ddos attacks

Well I have all that setup fine for now

My only issue was that some pages were not being hit and showing dynamic from the cf-cache-status

And then u can look into cache reserve

I'll check out cache reserve

I thought it was enterprise but I guess that's another cache feature

You could also go for cloudflare workers

The free tier is pretty generous if you site isn't clocking a lot of traffic

Yea I do use CF workers for a lot of things they are handy