[TYPO3-core] RFC: #10201: Duplicate cHash Values

Franz Koch typo.removeformessage at fx-graefix.de
Tue Mar 3 10:30:33 CET 2009


Hi,
>> What does core team think about it?
>>
>> I am in favor of using full md5(). It is correct from formal point of 
>> view. The only drawbacks that I see are:
>> - longer URLs
>> - sometimes 404 because of the wrong cHash if followed from Google
>>
> 
> i thought abot this and reread all BT entries concerning existing 
> problems with cHash. shortMD5 isn't unique, md5 is, so i'm for using 
> full md5. There are still some other problems remaining with empty 
> parameters, where a cHash should be generated too, but this is another 
> issue. But solving this one, the other problems should be solved too as 
> they are all related.

how about only appending a unique DB uid of stored cHashes to the URLs? 
Just as idea for getting nicer URLs in case of using full md5 hashes - 
haven't really thought about the pros and cons yet.

-- 
kind regards,
Franz Koch

---------------------------------------------------
PayPal-Account: 'paypal _at_ elements-net _dot_ de'
---------------------------------------------------


More information about the TYPO3-team-core mailing list