Problem/Motivation
The page cache id could be long, as the URL might be over 256 characters which were previously possible with the database cache backend.
This was however changed, the cid is automatically and more intelligently (the first part of the cid is kept) hashed.
Proposed resolution
Remove the call to sha1().
Advantage:
- We save a sha1() for all urls + content type < 256 character
Debugging the page cache is easier
Remaining tasks
User interface changes
API changes
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | remove-explicit-sha-2386255-3.patch | 3.84 KB | aneek |
| #5 | interdiff-2386255-2-3.txt | 3.41 KB | aneek |
| #2 | 2386255-2.patch | 435 bytes | rpayanm |
Comments
Comment #1
wim leersComment #2
rpayanmLet's me try :)
Comment #4
berdirPageCacheTagsTestBase has a sha1() call too, removing that should fix all the CacheTagsTests. BlockTest might have one too.
Comment #5
aneek commented@rpayanm,
There are more files that depends on removal of SHA1 as suggested by @Berdir.
Just uploading a patch removing these. Please fix if I've missed something.
Comment #6
aneek commentedComment #7
wim leersLooks great, thanks!
Comment #8
rpayanm@Berdir @aneek Thank you for you explanation :)
Comment #9
catchCommitted/pushed to 8.0.x, thanks!