Zend Cache TTL Default Fallback for Malformed Strings Before Version 3.3
0 reputation · 19 Mar 2022, 07:47 UTC
Zend Cache TTL Default Fallback for Malformed Strings Before Version 3.3
The goal is to determine whether the default TTL fallback applied when a malformed TTL string is supplied can be configured globally, or whether each cache instance must validate TTL input before writing.
Zend Cache accepts numeric seconds and human-readable TTL strings, but documentation does not state whether a malformed string triggers a warning or silently substitutes a default. Parsing behavior may differ between versions 2.5 and 3.0, and the fallback value may be hard-coded in earlier releases.
Is there a configuration directive to replace the fallback TTL? Does the silent fallback apply per backend instance or across the cache factory? What is the recommended method to detect malformed TTL values before they reach the parser?
zend