mirror of
https://github.com/django/django.git
synced 2025-08-04 02:48:35 +00:00
Removed versionadded/changed annotations dating back to 1.4.
This commit is contained in:
parent
ef017a5f00
commit
7ee7599ab3
49 changed files with 59 additions and 409 deletions
|
@ -39,8 +39,6 @@ a :class:`django.http.HttpResponseNotAllowed` if the conditions are not met.
|
|||
|
||||
.. function:: require_safe()
|
||||
|
||||
.. versionadded:: 1.4
|
||||
|
||||
Decorator to require that a view only accept the GET and HEAD methods.
|
||||
These methods are commonly considered "safe" because they should not have
|
||||
the significance of taking an action other than retrieving the requested
|
||||
|
|
|
@ -110,8 +110,6 @@ server has permissions to read and write to this location.
|
|||
Using cookie-based sessions
|
||||
---------------------------
|
||||
|
||||
.. versionadded:: 1.4
|
||||
|
||||
To use cookies-based sessions, set the :setting:`SESSION_ENGINE` setting to
|
||||
``"django.contrib.sessions.backends.signed_cookies"``. The session data will be
|
||||
stored using Django's tools for :doc:`cryptographic signing </topics/signing>`
|
||||
|
@ -558,9 +556,6 @@ consistently by all browsers. However, when it is honored, it can be a
|
|||
useful way to mitigate the risk of client side script accessing the
|
||||
protected cookie data.
|
||||
|
||||
.. versionchanged:: 1.4
|
||||
The default value of the setting was changed from ``False`` to ``True``.
|
||||
|
||||
.. _HTTPOnly: https://www.owasp.org/index.php/HTTPOnly
|
||||
|
||||
SESSION_COOKIE_NAME
|
||||
|
|
|
@ -26,10 +26,9 @@ This mapping can be as short or as long as needed. It can reference other
|
|||
mappings. And, because it's pure Python code, it can be constructed
|
||||
dynamically.
|
||||
|
||||
.. versionadded:: 1.4
|
||||
Django also provides a way to translate URLs according to the active
|
||||
language. See the :ref:`internationalization documentation
|
||||
<url-internationalization>` for more information.
|
||||
Django also provides a way to translate URLs according to the active
|
||||
language. See the :ref:`internationalization documentation
|
||||
<url-internationalization>` for more information.
|
||||
|
||||
.. _how-django-processes-a-request:
|
||||
|
||||
|
@ -246,9 +245,6 @@ The variables are:
|
|||
* ``handler500`` -- See :data:`django.conf.urls.handler500`.
|
||||
* ``handler403`` -- See :data:`django.conf.urls.handler403`.
|
||||
|
||||
.. versionadded:: 1.4
|
||||
``handler403`` is new in Django 1.4.
|
||||
|
||||
.. _urlpatterns-view-prefix:
|
||||
|
||||
The view prefix
|
||||
|
|
|
@ -199,8 +199,6 @@ One thing to note about 500 views:
|
|||
The 403 (HTTP Forbidden) view
|
||||
-----------------------------
|
||||
|
||||
.. versionadded:: 1.4
|
||||
|
||||
In the same vein as the 404 and 500 views, Django has a view to handle 403
|
||||
Forbidden errors. If a view results in a 403 exception then Django will, by
|
||||
default, call the view ``django.views.defaults.permission_denied``.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue