This Month in TYPO3: June 2025 [Issue #26]
TYPO3’s summer momentum is in full swing! The v14 release schedule is live, AI-integration planning is sparking excitement, five community-funded…
Intended Audience
This article is intended for TYPO3 administrators who are considering client-side caching of content to improve performance.
You should be able to install and configure TYPO3 and know about the basics of TypoScript.
How it started
The Danish Consumer Agency runs the consumers' portal <link http: www.forbrug.dk _blank>forbrug.dk which is one of the largest TYPO3 installations in the world with 130,000 unique visitors giving 13 million hits per month.
This was managed with only 1 server for the website and database and 1 server for delivering mail. During the fall 2004 they experienced spikes in their traffic (usually caused by being mentioned on TV and net media). These spikes were more than the installation could handle.
Possible solutions
Upgrading the CPUs in the server was quickly ruled out as a solution: Doubling the speed would have cost at least 15,000 Euro in hardware alone.
So a software solution was needed. They analyzed their documents and most of them are not changed during 24 hours – these could be cached without any problems. A few, however, must never be cached as they change (e.g. the result of a search).
„We tried making a small change where all pages were cached for 24 hours using Apache's proxy module as caching engine. While this gave a remarkable speed up (in the order of 10 times) this proved fatal to the few pages that must never cached.
The right thing to do was of course to make TYPO3 compliant with current caching practices (e.g. RFC-2616). After identifying the changes needed in term of HTTP-headers that should be generated, we turned to Kasper Skårhøj and had him implement the changes. The identification process took in the order of a man week, and implementing the changes in TYPO3 and testing them took also in the order of a man week.“ (Ole Tange, www.forbrug.dk)
The page was cached by TYPO3
No *_INT or *_EXT objects were on the page (e.g. USER_INT)
No frontend user is logged in
No backend user is logged in
TYPO3’s summer momentum is in full swing! The v14 release schedule is live, AI-integration planning is sparking excitement, five community-funded…
Artificial Intelligence is no longer just a trend — it's becoming a key component in many CMS environments. Interest in AI-powered features for…
Jeffrey A. “jam” McGuire explores TYPO3’s journey from “survival” to “resurrection” and its global impact through democratic open source governance at…
In early May, over 30 TYPO3 community members from across Europe gathered on the island of Fuerteventura for a week full of coding, learning, and…
We are pleased to announce that all official TYPO3 certifications are now available for TYPO3 v13. This includes updated exams for the four major…
The TYPO3 Association member poll for the Q3/2025 budget ideas has been finished and this time five winning ideas will be funded by the TYPO3…