Caching not working? Cloudflare interfering?

Troubleshooting and help
,
1

I’ve set what I believe are appropriate cache headers in my Node Express app on Koyeb. This is proven by doing a CURL -I to a live image link for my app on Koyeb, and seeing the cache-control headers return what I set them at, but also shows CF-Cache-Status: MISS. When looking at it in Chrome Dev Tools though, I see

request headers said this:

cache-control:
no-cache
dnt:
1
pragma:
no-cache

response headers said this:

cache-control:
public, max-age=0

cf-cache-status:
MISS

2

To clarify my post (since it may have been hard to figure out what I was asking) - is caching broken with Koyeb? Am I doing something wrong?

I’ve set what I believe are the right headers etc, based on a blog post from Koyeb about HTTP headers for caching. And my curl request seems to show the caching settings were done correctly.

However, the live site clearly doesn’t seem have caching working, and it appears to be due to cloudflare (I’m not using cloudflare - I guess Koyeb is?).

If there’s anything I’m missing here, please let me know.

3

Hey,

We disabled Cloudflare caching months ago, so it’s not possible to use those headers as of today. If you really need caching, a workaround is described here: Koyeb CDN Ignores max-age Cache-Control headers.

Is Using Cache-Control and CDNs to Improve Performance and Reduce Latency - Koyeb the blog post you were reading? We will update it to make it clear this is not something we currently support.

1 Like
4

Many thanks. Yes that was the blog post in question.

It sounds like the forced workaround mentioned in the other post for caching isn’t such a good solution, as it sounds like it adds an extra 60~90ms latency. So I guess I’ll just do without.

Good to know, as if Koyeb doesn’t intend to add any kind of caching then it’s probably better for me to remove the code in my app that creates/deals with caching protocols