While MD5 is "broken" in a cryptographic sense, it's not broken in the
sense that we use it here. A randomly occurring hash collision is
extremely unlikely (to the point of not being a problem). If we warned
about potential hash collisions here, we (and everyone else who uses
hashes) would have to
Hi all,
The current implementation of the 'cache' templatetag [1] uses an MD5
hash derived from the vary_on arguments to create a unique cache_key
for the current template fragment.
However, this approach has the possibility of a hash collision. While
not very likely, this might nonetheless expos
