mirror of
https://github.com/django/django.git
synced 2025-09-26 12:09:19 +00:00
Fixed #4992 -- Respect the GET request query string when creating cache keys. Thanks PeterKz and guettli for the initial patch.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@15705 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
a9ace1466d
commit
f6c991667f
6 changed files with 57 additions and 15 deletions
|
@ -962,9 +962,13 @@ mechanism should take into account when building its cache key. For example, if
|
|||
the contents of a Web page depend on a user's language preference, the page is
|
||||
said to "vary on language."
|
||||
|
||||
.. versionchanged:: 1.3
|
||||
In Django 1.3 the full request path -- including the query -- is used
|
||||
to create the cache keys, instead of only the path component in Django 1.2.
|
||||
|
||||
By default, Django's cache system creates its cache keys using the requested
|
||||
path (e.g., ``"/stories/2005/jun/23/bank_robbed/"``). This means every request
|
||||
to that URL will use the same cached version, regardless of user-agent
|
||||
path and query -- e.g., ``"/stories/2005/?order_by=author"``. This means every
|
||||
request to that URL will use the same cached version, regardless of user-agent
|
||||
differences such as cookies or language preferences. However, if this page
|
||||
produces different content based on some difference in request headers -- such
|
||||
as a cookie, or a language, or a user-agent -- you'll need to use the ``Vary``
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue