We couldn't come up with a solution when
discussing this with Erik,
hence this thread.
I wonder if this can not be solved by some kind of redirect
configuration, i.e. the initial URL U is modified to U' so that when U'
is accessed, it is recorded and then redirected to cacheable URL U. This
way, we have the record of U' being accessed, thus having the it
available for analytics, but U is still served from cache. That would,
of course, work best if we could make the frontend servers do the
redirect, and one redirect should be much faster than loading non-cached
I'm not sure which form of U' would be the best, or if it is feasible,
just putting it out for discussion.