Cache key immediate expiration – redis conflict?
-
We are using this plugin to cache our api requests but are finding that the cached queries show in the dashboard as being expired. This is despite the record in the database having the correct expiration date, being 1 year in the future.
Our setup is also using redis for caching and think that we have isolated this as the cause of the issue. Disabling redis we get our api queries being served via the cache and the dashboard shows the correct expiration but without it it’s broken.
Does anyone have any experience using redis with this plugin? Any help would be great!
Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
- The topic ‘Cache key immediate expiration – redis conflict?’ is closed to new replies.