Blog Sections Open
Using Last-Modified and If-Modified-Since Headers in Evolution CMS
Conditional HTTP headers can reduce repeated page transfers, but only if the timestamp logic matches the real lifetime of your content.
Last-Modified and If-Modified-Since are useful when you want browsers or proxies to avoid re-downloading unchanged content. In Evolution CMS, that means deciding which timestamp truly represents the page state.
Typical candidates
- resource
editedon - resource
publishedon - a derived timestamp from related data
Recommendation
Only add conditional headers when you control the real invalidation rules. If a page depends on listings, menus, comments, or external data, a naive resource timestamp can easily become misleading.
Choosing a JS and CSS Minification Strategy in Evolution CMS
Minification works best when you know whether you need automatic page-level aggregation, explicit asset lists, or optimization only for registered front-end files.
Fixing Named Anchor Conflicts with jQuery UI Tabs and base href
If jQuery UI tabs start loading the home page instead of switching locally, look at how named anchors interact with base href and relative links.