Memcache storage service does not correctly delete contexts
Basics
Technical
Logistics
Basics
Technical
Logistics
Description
While running the memcached server in verbose mode to inspect the traffic being sent to it from Shibboleth, I noticed that MemcacheStorageService::deleteContext does not correctly delete the individual elements from the context.
Below is sample memcached traffic generated by a call to MemcacheStorageService::deleteContext() to delete a session context with a single key, "session":
The context map correctly lists the "session" field, but there is a ":" missing between the context ID and the keys to be deleted:
Session data that otherwise would have been deleted therefore stays present on the memcached host, causing unnecessary resource pressure.
Environment
None
Activity
Show:
Scott Cantor May 11, 2016 at 2:04 AM
aac629d04087e8bfdf0fd9caced172b2023cb83a
I assume all that's needed is adding the colon between the two halves. I didn't write the plugin and don't have any experience with it, so I'm not too familiar with the workings.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
While running the memcached server in verbose mode to inspect the traffic being sent to it from Shibboleth, I noticed that MemcacheStorageService::deleteContext does not correctly delete the individual elements from the context.
Below is sample memcached traffic generated by a call to MemcacheStorageService::deleteContext() to delete a session context with a single key, "session":
The context map correctly lists the "session" field, but there is a ":" missing between the context ID and the keys to be deleted:
Session data that otherwise would have been deleted therefore stays present on the memcached host, causing unnecessary resource pressure.