#31654: Memcached key validation raises InvalidCacheKey with clunky message.
-------------------------------------+------------------------------------
Reporter: Tim McCormack | Owner: felixxm
Type: Bug | Status: assigned
Component: Core (Cache system) | Version: 2.2
Severity: Normal | Resolution:
Keywords: memcached | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by felixxm):
* owner: nobody => felixxm
* status: new => assigned
* stage: Unreviewed => Accepted
Comment:
Thanks for the report, we've already noticed this, see
[https://github.com/django/django/pull/13017 PR]. It raises
`InvalidCacheKey` for me (even if a message is not perfect), e.g.
{{{
File "django/core/cache/backends/memcached.py", line 157, in validate_key
raise InvalidCacheKey(warning)
django.core.cache.backends.base.InvalidCacheKey: ("Cache key contains
characters that will cause errors if used with memcached:
'38_postgis_pull-requests-bionic_memcache:1:key with spaces and 清'",
<class 'django.core.cache.backends.base.CacheKeyWarning'>)
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31654#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.ac09885682d0bea14380f72c3ade2db7%40djangoproject.com.
