You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2018. It is now read-only.
The Problem is that there will always an array be stored at the memcache server.
There should be an option to store a raw string since automatic_serialization has no affect here.
My hotfix is to remove time() and $lifetime. Since this results in problems for the session memcached handler i use an custom backend for the fix.
In my setup im reading values stored in memcached directly using the NGINX memcached extension and the $request_uri as memcache key.
If the memcache server has a key matching the $request_uri then the content is directly delivered to the user.
This response will include time() and $lifetime values stored in memcache by the Zend Framework Backend Class. Only if the NGINX memcached Extension has no cache hit the php-fpm backend is called.
The text was updated successfully, but these errors were encountered:
Jira Information
Description
In Zend_Cache_Backend_Libmemcached::save() and Zend_Cache_Backend_Memcached::save()
You will find the following line:
The Problem is that there will always an array be stored at the memcache server.
There should be an option to store a raw string since automatic_serialization has no affect here.
My hotfix is to remove time() and $lifetime. Since this results in problems for the session memcached handler i use an custom backend for the fix.
In my setup im reading values stored in memcached directly using the NGINX memcached extension and the $request_uri as memcache key.
If the memcache server has a key matching the $request_uri then the content is directly delivered to the user.
This response will include time() and $lifetime values stored in memcache by the Zend Framework Backend Class. Only if the NGINX memcached Extension has no cache hit the php-fpm backend is called.
The text was updated successfully, but these errors were encountered: