c23a66f66d3a9bf64276607cd01ca9ab466077f1
Commit Graph

3 Commits

Author SHA1 Message Date
Peter Portante
6e313e957d Fix for memcache middleware configuration 
The documentation rightly said to use "memcache_max_connections", but
the code was looking for "max_connections", and only looking for it in
proxy-server.conf, not in memcache.conf as a fall back.
This commit brings the code coverage for the memcache middleware to
100%.
Closes-Bug: 1252893
Change-Id: I6ea64baa2f961a09d60b977b40d5baf842449ece
Signed-off-by: Peter Portante <peter.portante@redhat.com>
 2013年11月26日 18:03:33 +00:00
Vincent Untz
e1ff51c045 Do not use pickle for serialization in memcache, but JSON 
We don't want to use pickle as it can execute arbitrary code. JSON is
safer. However, note that it supports serialization for only some
specific subset of object types; this should be enough for what we need,
though.
To avoid issues on upgrades (unability to read pickled values, and cache
poisoning for old servers not understanding JSON), we add a
memcache_serialization_support configuration option, with the following
values:
 0 = older, insecure pickle serialization
 1 = json serialization but pickles can still be read (still insecure)
 2 = json serialization only (secure and the default)
To avoid an instant full cache flush, existing installations should
upgrade with 0, then set to 1 and reload, then after some time (24
hours) set to 2 and reload. Support for 0 and 1 will be removed in
future versions.
Part of bug 1006414.
Change-Id: Id7d6d547b103b4f23ebf5be98b88f09ec6027ce4
 2012年08月03日 16:22:21 +02:00
gholt
338be6a681 Added memcache.conf option 
Change-Id: Idfcb97421a5c1476b776acef94c7b997dab55aa9
 2012年01月10日 02:01:47 +00:00