Michael Dever wrote: > Or is there a way to set a low lifetime on anthing thAt is a feed? > Like maybe a minute? The problem would still be there, but reduced.
I don't believe there is any lifetime option for the Rails page caching feature that Typo uses. However ... >> So my guess is that this happens whenever a URL like >> >> http://your.blog.org/?format=rss >> >> (which caches like index.html!) is accessed before >> >> http://your.blog.org/ >> >> gets a chance to cache its version. I don't really see a solution for this: >> Is >> there a way to make Rails ignore parameters supplied this way? ... I have come up with a solution for this quandary! It is possible to add a condition to Rails' page caching. I have just implemented the condition that the query string must be empty. This means that *after a cache sweep*, http://your.blog.org/?format=rss will return the RSS feed but will not cache anything. Then, http://your.blog.org/ will return the proper html and cache it. Then http://your.blog.org/?format=rss will return the html. This is not what the client requested, but they shouldn't be accessing the rss feed like that anyway, so I consider this a minor problem, and certainly a lot less bad than the current situation. I've committed the fix to typo's master branch. -- Matijs
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Typo-list mailing list Typo-list@rubyforge.org http://rubyforge.org/mailman/listinfo/typo-list
