Several of Django's built-in views are documented in\nWriting views as well as elsewhere in the documentation.
\nThere may be files other than your project's static assets that, for\nconvenience, you'd like to have Django serve for you in local development.\nThe serve() view can be used to serve any directory\nyou give it. (This view is not hardened for production use and should be\nused only as a development aid; you should serve these files in production\nusing a real front-end web server).
The most likely example is user-uploaded content in MEDIA_ROOT.\ndjango.contrib.staticfiles is intended for static assets and has no\nbuilt-in handling for user-uploaded files, but you can have Django serve your\nMEDIA_ROOT by appending something like this to your URLconf:
from django.conf import settings\nfrom django.views.static import serve\n\n# ... the rest of your URLconf goes here ...\n\nif settings.DEBUG:\n urlpatterns += [\n url(r'^media/(?P<path>.*)$', serve, {\n 'document_root': settings.MEDIA_ROOT,\n }),\n ]\nNote, the snippet assumes your MEDIA_URL has a value of\n'/media/'. This will call the serve() view,\npassing in the path from the URLconf and the (required) document_root\nparameter.
Since it can become a bit cumbersome to define this URL pattern, Django\nships with a small URL helper function static()\nthat takes as parameters the prefix such as MEDIA_URL and a dotted\npath to a view, such as 'django.views.static.serve'. Any other function\nparameter will be transparently passed to the view.
Django comes with a few views by default for handling HTTP errors. To override\nthese with your own custom views, see Customizing error views.
\nWhen you raise Http404 from within a view, Django loads a\nspecial view devoted to handling 404 errors. By default, it's the view\ndjango.views.defaults.page_not_found(), which either produces a very\nsimple "Not Found" message or loads and renders the template 404.html if\nyou created it in your root template directory.
The default 404 view will pass two variables to the template: request_path,\nwhich is the URL that resulted in the error, and exception, which is a\nuseful representation of the exception that triggered the view (e.g. containing\nany message passed to a specific Http404 instance).
Three things to note about 404 views:
\nThe 404 view is also called if Django doesn't find a match after\nchecking every regular expression in the URLconf.
The 404 view is passed a RequestContext and\nwill have access to variables supplied by your template context\nprocessors (e.g. MEDIA_URL).
If DEBUG is set to True (in your settings module), then\nyour 404 view will never be used, and your URLconf will be displayed\ninstead, with some debug information.
Similarly, Django executes special-case behavior in the case of runtime errors\nin view code. If a view results in an exception, Django will, by default, call\nthe view django.views.defaults.server_error, which either produces a very\nsimple "Server Error" message or loads and renders the template 500.html if\nyou created it in your root template directory.
The default 500 view passes no variables to the 500.html template and is\nrendered with an empty Context to lessen the chance of additional errors.
If DEBUG is set to True (in your settings module), then\nyour 500 view will never be used, and the traceback will be displayed\ninstead, with some debug information.
In the same vein as the 404 and 500 views, Django has a view to handle 403\nForbidden errors. If a view results in a 403 exception then Django will, by\ndefault, call the view django.views.defaults.permission_denied.
This view loads and renders the template 403.html in your root template\ndirectory, or if this file does not exist, instead serves the text\n"403 Forbidden", as per RFC 7231 Section 6.5.3 (the HTTP 1.1 Specification).\nThe template context contains exception, which is the unicode\nrepresentation of the exception that triggered the view.
django.views.defaults.permission_denied is triggered by a\nPermissionDenied exception. To deny access in a\nview you can use code like this:
from django.core.exceptions import PermissionDenied\n\ndef edit(request, pk):\n if not request.user.is_staff:\n raise PermissionDenied\n # ...\nWhen a SuspiciousOperation is raised in Django,\nit may be handled by a component of Django (for example resetting the session\ndata). If not specifically handled, Django will consider the current request a\n'bad request' instead of a server error.
django.views.defaults.bad_request, is otherwise very similar to the\nserver_error view, but returns with the status code 400 indicating that\nthe error condition was the result of a client operation. By default, nothing\nrelated to the exception that triggered the view is passed to the template\ncontext, as the exception message might contain sensitive information like\nfilesystem paths.
bad_request views are also only used when DEBUG is False.