Rip out pickle support in our memcached client

Code Issues Proposed changes

We said this would be going away back in 1.7.0 -- lets actually remove it.
Change-Id: I9742dd907abea86da9259740d913924bb1ce73e7
Related-Change: Id7d6d547b103b4f23ebf5be98b88f09ec6027ce4

This commit is contained in:

Tim Burke

2020年06月18日 10:29:15 -07:00

parent b621a6f932

commit 11b9761cdf

7 changed files with 23 additions and 150 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

15
doc/manpages/proxy-server.conf.5

View File

@@ -415,21 +415,6 @@ read from /etc/swift/memcache.conf (see memcache.conf-sample) or lacking that

file, it will default to 127.0.0.1:11211. You can specify multiple servers

separated with commas, as in: 10.1.2.3:11211,10.1.2.4:11211. (IPv6

addresses must follow rfc3986 section-3.2.2, i.e. [::1]:11211)

.IP \fBmemcache_serialization_support\fR

This sets how memcache values are serialized and deserialized:

.RE

.PD 0

.RS 10

.IP "0 = older, insecure pickle serialization"

.IP "1 = json serialization but pickles can still be read (still insecure)"

.IP "2 = json serialization only (secure and the default)"

.RE

.RS 10

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. In the future, the ability to use pickle serialization will be removed.

If not set in the configuration file, the value for memcache_serialization_support will be read from /etc/swift/memcache.conf if it exists (see memcache.conf-sample). Otherwise, the default value as indicated above will be used.

.RE

.PD

Rip out pickle support in our memcached client

15 doc/manpages/proxy-server.conf.5 Unescape Escape View File

15
doc/manpages/proxy-server.conf.5

View File