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
that Typo uses.
So my guess is that this happens whenever a URL like
(which caches like index.html!) is accessed before
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
condition to Rails’ page caching. I have just implemented the condition
query string must be empty. This means that after a cache sweep,
will return the RSS feed but will not cache anything. Then,
will return the proper html and cache it. Then
will return the html. This is not what the client requested, but they
be accessing the rss feed like that anyway, so I consider this a minor
and certainly a lot less bad than the current situation.
I’ve committed the fix to typo’s master branch.