#20346: cache middleware should vary on full URL
-------------------------------------+------------------------------------
Reporter: jamey | Owner:
Type: Bug | Status: new
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by timo):
* needs_better_patch: 0 => 1
* version: 1.3 => master
* needs_tests: 1 => 0
* needs_docs: 0 => 1
Comment:
Here's an [https://code.djangoproject.com/ticket/20346 updated PR] with
tests. I left some minor comments for improvement.
One concern is that upgrading Django will change cache keys for all the
existing pages now that the domain name is part of the key. At a minimum,
this needs to be documented in the release notes. Ideas for how we might
be able to do this in a backwards compatible fashion would also be
welcome.
--
Ticket URL: <https://code.djangoproject.com/ticket/20346#comment:8>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.17026273d825f00c156e4a095977789f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
