Cloudflare disrespecting max-age header even when Browser Cache TTL is set to 'Respect Existing Headers'

Website, Application, Performance
1

Hi,
We have our website at https://skillmamba.com configured to use Cloudflare load balancer and use origins at https://in.skillmamba.com and https://us.skillmamba.com

Both the origins set max-age=600 but when using https://skillmamba.com in a browser, i get http status 304 on every subsequent request after the first one, even after 600 seconds have passed, the ‘age’ header keeps going beyond 600.

Should it not fetch a fresh copy after 600 seconds have elapsed?

I believe it is a Cloudflare thing as accessing https://in.skillmamba.com or https://us.skillmamba.com directly doesn’t give me any such problem.

What am i doing wrong? Please help. Thanks.

4

Also, the issue disappears if i pause Cloudflare by entering ‘Development Mode’.

5

Hello! This is expected behaviour as you’re using APO.

APO does not respect cache control header directive for Edge Caching.

APO will cache your pages for 30 days and revalidate it 30+ seconds after an update.

4 Likes
6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.