More questions about caching mechanism

Gizmo

Hi @mad !
I want to ask you about caching mechanism since there is not much info in Automad's docs.
I have caching enabled in the dashboard but:
1) Should I enable caching and compression in htaccess file based on static file types?
2) Should I enable caching and compression in CPanel or ISPManager which will trigger nginx mechanism?
3) Maybe I should use all of those together?

Also I see some "cache-busting" technique applied for standard.min.js and for standard.min.css.
Which means I should not unset ETag headers via htaccess? Or not? Or what?)))

mad

Gizmo Hi, the caching in Automad is unrelated to the standard compression or caching that optimizes network traffic. Automad has several levels of caching that in the end produce static html pages. The validation whether a page has to be rendered or can be served from cache is handled automatically as long as caching is enabled. So in other words, Automad tries to reduce render times significantly by caching its output and only server static files with a little overhead caused by the validation.
Therefore it doesn’t conflict with other caching mechanisms. However I don’t think it is necessary to worry about additional caching.

Gizmo

mad
Thanks for clarification. Can you please add a bit more details about what automad does with versioning/caching of css/js/images? Looks like it does something with all statics which were added thru dashboard.
What I mean is that almost all static resources Automad renders for example as *.css?m=1667865242 and sets ETag for it and does not provide Cache TTL via Header Cache-Control which is wrong I think.

Why Automad versioning/quering ctandard.css and standard.js if they never change and are always same?
The same is for uploaded content. Why versioning/quering uploaded images added to user's post/page if they will stay there forever in most cases?

Also I can't change this behavior with htaccess for some reason. But for good practice we must use for static with ETag Header Cache-Control and stale-while-revalidate. Or even better use Header Cache-Control: max-age=31536000, immutable for all static content. Can we achive this somehow?
Here is some good reading about this case - https://simonhearne.com/2022/caching-header-best-practices/