diff options
| author | Kevin Christopher Henry <k@severian.com> | 2016-09-01 09:32:20 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-09-10 08:14:52 -0400 |
| commit | 4ef0e019b7dd3d2bf93b5c705b3b7df9cdb77561 (patch) | |
| tree | 3b87b0f6df6ca459833f0569df3c2f6320ff4d67 /docs | |
| parent | e7abb5ba8608f90ce97c6edb031ae877195616f5 (diff) | |
Fixed #27083 -- Added support for weak ETags.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.11.txt | 3 | ||||
| -rw-r--r-- | docs/topics/conditional-view-processing.txt | 8 |
2 files changed, 11 insertions, 0 deletions
diff --git a/docs/releases/1.11.txt b/docs/releases/1.11.txt index afd24e6613..49d0516b99 100644 --- a/docs/releases/1.11.txt +++ b/docs/releases/1.11.txt @@ -491,6 +491,9 @@ Miscellaneous * The admin's widget for ``IntegerField`` uses ``type="number"`` rather than ``type="text"``. +* ETags are now parsed according to the :rfc:`7232` Conditional Requests + specification rather than the syntax from :rfc:`2616`. + .. _deprecated-features-1.11: Features deprecated in 1.11 diff --git a/docs/topics/conditional-view-processing.txt b/docs/topics/conditional-view-processing.txt index 7efd8ac636..7398b3fd05 100644 --- a/docs/topics/conditional-view-processing.txt +++ b/docs/topics/conditional-view-processing.txt @@ -66,6 +66,14 @@ last time the resource was modified, or ``None`` if the resource doesn't exist. The function passed to the ``etag`` decorator should return a string representing the `ETag`_ for the resource, or ``None`` if it doesn't exist. +.. 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:: |