===============View decorators===============.. module:: django.views.decorators.httpDjango provides several decorators that can be applied to views to supportvarious HTTP features.See :ref:`decorating-class-based-views` for how to use these decorators withclass-based views.Allowed HTTP methods====================The decorators in :mod:`django.views.decorators.http` can be used to restrictaccess to views based on the request method. These decorators will returna :class:`django.http.HttpResponseNotAllowed` if the conditions are not met... function:: require_http_methods(request_method_list)Decorator to require that a view only accepts particular requestmethods. Usage::from django.views.decorators.http import require_http_methods@require_http_methods(["GET", "POST"])def my_view(request):# I can assume now that only GET or POST requests make it this far# ...passNote that request methods should be in uppercase... function:: require_GET()Decorator to require that a view only accepts the GET method... function:: require_POST()Decorator to require that a view only accepts the POST method... function:: require_safe()Decorator to require that a view only accepts the GET and HEAD methods.These methods are commonly considered "safe" because they should not havethe significance of taking an action other than retrieving the requestedresource... note::Web servers should automatically strip the content of responses to HEADrequests while leaving the headers unchanged, so you may handle HEADrequests exactly like GET requests in your views. Since some software,such as link checkers, rely on HEAD requests, you might preferusing ``require_safe`` instead of ``require_GET``.Conditional view processing===========================The following decorators in :mod:`django.views.decorators.http` can be used tocontrol caching behavior on particular views... function:: condition(etag_func=None, last_modified_func=None).. function:: etag(etag_func).. function:: last_modified(last_modified_func)These decorators can be used to generate ``ETag`` and ``Last-Modified``headers; see:doc:`conditional view processing </topics/conditional-view-processing>`... module:: django.views.decorators.gzipGZip compression================The decorators in :mod:`django.views.decorators.gzip` control contentcompression on a per-view basis... function:: gzip_page()This decorator compresses content if the browser allows gzip compression.It sets the ``Vary`` header accordingly, so that caches will base theirstorage on the ``Accept-Encoding`` header... module:: django.views.decorators.varyVary headers============The decorators in :mod:`django.views.decorators.vary` can be used to controlcaching based on specific request headers... function:: vary_on_cookie(func).. function:: vary_on_headers(*headers)The ``Vary`` header defines which request headers a cache mechanism should takeinto account when building its cache key.See :ref:`using vary headers <using-vary-headers>`... module:: django.views.decorators.cacheCaching=======The decorators in :mod:`django.views.decorators.cache` control server andclient-side caching... function:: cache_control(**kwargs)This decorator patches the response's ``Cache-Control`` header by addingall of the keyword arguments to it. See:func:`~django.utils.cache.patch_cache_control` for the details of thetransformation... function:: never_cache(view_func)This decorator adds an ``Expires`` header to the current date/time.This decorator adds a ``Cache-Control: max-age=0, no-cache, no-store,must-revalidate, private`` header to a response to indicate that a pageshould never be cached.Each header is only added if it isn't already set... module:: django.views.decorators.commonCommon======The decorators in :mod:`django.views.decorators.common` allow per-viewcustomization of :class:`~django.middleware.common.CommonMiddleware` behavior... function:: no_append_slash()This decorator allows individual views to be excluded from:setting:`APPEND_SLASH` URL normalization.