CachingFramework should accept cacheIdentifiers with special characters
|Priority:||Should have||Due date:|
Currently the CachingFramework throws an exception if the specified cacheIdentifier contains a backslash for example.
This leads to the fact that we are (sometimes faultily) escaping the identifier in various places.
Instead the CachingFramework should handle this in a central place.
Updated by Robert Lemke 7 months ago
- Status changed from New to Closed
- Has patch set to No
My suggestion: use md5() or an escaping function to sanitize the identifier (if possible). I'd rather not put it into the frontend itself because it adds unneccessary overhead for those cases where escaping is not needed.
Re-open if you don't agree.