Dave Cheney wrote:
md5 is not guaranteed to be unique, that is to say, two seperate
inputs can generate the same hash, so you would need to use extra
logic in your application if you wanted to guard against this remote
possibility. I'm guessing the problem you are trying to solve is the
memcache key has a limitation that is shorter than the possible
request_uri ?
Cheers
Thanks Dave,
The problem is that memcached will not allow certain characters in the
key name - so I thought it might be simpler to just store the md5 of the
actual request_uri.
Thanks,
Geoff
6 messages in ru.sysoev.nginxRe: md5 as memcached_key