summaryrefslogtreecommitdiff
path: root/docs/topics/conditional-view-processing.txt
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2017-09-02 21:49:07 -0400
committerTim Graham <timograham@gmail.com>2017-09-22 12:51:18 -0400
commit5446b72003790fc98bd926f7196b26cc5db63c5a (patch)
tree0ff9fe34b7f6c1c79e84d8f4fbea52fdfeb0baf3 /docs/topics/conditional-view-processing.txt
parent2bd207ada0367debe8c8e298203435d5c88c14bd (diff)
Removed versionadded/changed annotations for 1.11.
Diffstat (limited to 'docs/topics/conditional-view-processing.txt')
-rw-r--r--docs/topics/conditional-view-processing.txt8
1 files changed, 0 insertions, 8 deletions
diff --git a/docs/topics/conditional-view-processing.txt b/docs/topics/conditional-view-processing.txt
index 935c33be34..9016cd3b02 100644
--- a/docs/topics/conditional-view-processing.txt
+++ b/docs/topics/conditional-view-processing.txt
@@ -70,14 +70,6 @@ The decorator sets the ``ETag`` and ``Last-Modified`` headers on the response
if they are not already set by the view and if the request's method is safe
(``GET`` or ``HEAD``).
-.. versionchanged:: 1.11
-
- In older versions, the return value from ``etag_func()`` was interpreted as
- the unquoted part of the ETag. That prevented the use of weak ETags, which
- have the format ``W/"<string>"``. The return value is now expected to be
- an ETag as defined by the specification (including the quotes), although
- the unquoted format is also accepted for backwards compatibility.
-
Using this feature usefully is probably best explained with an example.
Suppose you have this pair of models, representing a simple blog system::