Dynamic resizing should apply to all hashes

Bug #769764 reported by François Marier on 2011-04-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libravatar
Wishlist
Unassigned

Bug Description

If an image referred to by an MD5 hash is dynamically resized, Libravatar will cache the resulting image so that next time it will be served from disk instead of generated again. This is currently only done for the hash that was requested while the same image might be available under more than one hash (e.g. md5 and sha256 for the same email address, or the md5 hashes of two different email addresses).

There is no way of course to "unhash" a hashed email address and rehash it using a different algorithm, but we can use the filesystem to tell us which files are the same:

- look up the inode number of the first hash using "ls -i"
- then find the other hashes using "find -mount -inum xxxxx"

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers