On 21.10.2005 08:54, Bart Molenkamp wrote:
How is this problem related to caching? It is not that hard for me to
provide a patch which just generates a new identifier, but I'm wondering
if it breaks caching...
It is related to caching as the cache key is only based on the request
uri and the fragment id. So with always the same uri and id you will
always get the same content from the cache.
Unfortunately nobody ever responded to my proposals about fixing it.
Jörg
Van: Joerg Heinicke
Verzonden: donderdag 20 oktober 2005 20:35
My problem is that the id is based on the request uri (and the number of
fragments that it extracts during a single transformation).
http://issues.apache.org/bugzilla/show_bug.cgi?id=28724
