[Typo3] performance, cache-control headers and published static pages

[christian reiter]

"tapio" <tapio.markula at dnainternet.net> schrieb
>
> How that could work with RealUrl plugin?

Um, right now it absolutely doesn´t - it works with Simulate Static. If the
checkbox "Allow Static caching" is checked for a page (which is only
possible if certain conditions of page and content are fulfilled, some
pagetypes like external URL, shortcut, mountpage etc. do not offer the
checkbox, and if the page contains dynamic plugins, it is also not offered)
then it is possible to publish a static file from the test to the live
server like "445.0.html" along with the database content, when the page is
published. Static caching is never done on the test server. a htaccess file
on the live server uses rewrite to simply looks for the static file first,
and if it is not found passes the request on to typo3. If typo3 renders the
page, caches it and finds the static option is set (that´s the hook in the
caching function) it will automatically refresh a static cached page that
has been lost (i.e. by manual intervention or a "delete static cache"
command passed from the test to live server). If the option is not set Typo3
works as usual.
All this depends on using the ID in the URL.
I have no experience working with RealURL and so I can´t say whether it
would be as simple to just extend the hooks to be able to create a file in
the complete path as created by RealURL and then let the htaccess on the
live server first look for that and then pass the request to typo3.

Christian