Removed versionadded/changed annotations for 1.9.

Using ``REMOTE_USER`` on login pages only

=========================================

.. versionadded:: 1.9

The ``RemoteUserMiddleware`` authentication middleware assumes that the HTTP

request header ``REMOTE_USER`` is present with all authenticated requests. That

might be expected and practical when Basic HTTP Auth with ``htpasswd`` or other

method after any path information is removed. Override this to customize how

non-standard characters are converted to safe filenames.

.. versionchanged:: 1.9

    In older versions, this method was not called when ``upload_to`` was a

    callable.

The code provided on ``Storage`` retains only alpha-numeric characters, periods

and underscores from the original filename, removing everything else.

    register = template.Library()

.. versionadded:: 1.9

Alternatively, template tag modules can be registered through the

``'libraries'`` argument to

:class:`~django.template.backends.django.DjangoTemplates`. This is useful if

use of :func:`~django.utils.html.format_html` instead of ``mark_safe()`` is

strongly recommended.

.. versionchanged:: 1.9

   Auto-escaping for ``simple_tag`` as described in the previous two paragraphs

   was added.

If your template tag needs to access the current context, you can use the

``takes_context`` argument when registering your tag::

    {% my_tag 123 "abcd" book.title warning=message|lower profile=user.profile %}

.. versionadded:: 1.9

It's possible to store the tag results in a template variable rather than

directly outputting it. This is done by using the ``as`` argument followed by

the variable name. Doing so enables you to output the content yourself where

ignores 404s when the referer is equal to the requested URL, since this

behavior is from broken Web bots too.

.. versionchanged:: 1.9

    In older versions, 404s were not ignored when the referer was equal to the

    requested URL.

.. note::

    :class:`~django.middleware.common.BrokenLinkEmailsMiddleware` must appear

You can also use the ``DJANGO_TEST_PROCESSES`` environment variable for this

purpose.

.. versionadded:: 1.9

    Support for running tests in parallel and the ``--parallel`` option were

    added.

Tips for writing tests

----------------------