Editoria11y cache tags are too long for Akamai on pages with long paths

...fwiw my prolonged silence is me wondering if I can be a little more lightweight here. This many cache tags down on a cache tag that is only set for logged-in content editors and only invalidated if someone dismisses a manual check (...rare)...it wouldn't be a big deal of a couple extra pages got matched for invalidation...so rather than using an MD5+b64 conversion, I could probably just change the string truncation from the first 1,000 characters to something like the last 20.

Thoughts?

Ah - I see. My concern was that the first 100 or so characters of various deep in the menu paths would be the same and I wanted to avoid conflicts. If these cache tags will be relatively rare (not all pages) - perhaps the truncation of the last 80 or so characters of the path? (Well under Akamai's limit but also more insurance that it would be unique.)

Fixed in 2.1.19 →

@itmaybejj would you mind sharing credit?

Oh I thought that happened automatically through commit credits