Django comes with an optional redirects application. It lets you store\nredirects in a database and handles the redirecting for you. It uses the HTTP\nresponse status code 301 Moved Permanently by default.
To install the redirects app, follow these steps:
\nEnsure that the django.contrib.sites framework\nis installed.
Add 'django.contrib.redirects' to your INSTALLED_APPS\nsetting.
Add 'django.contrib.redirects.middleware.RedirectFallbackMiddleware'\nto your MIDDLEWARE setting.
Run the command manage.py migrate.
manage.py migrate creates a django_redirect table in your database.\nThis is a lookup table with site_id, old_path and new_path fields.
The RedirectFallbackMiddleware\ndoes all of the work. Each time any Django application raises a 404\nerror, this middleware checks the redirects database for the requested\nURL as a last resort. Specifically, it checks for a redirect with the\ngiven old_path with a site ID that corresponds to the\nSITE_ID setting.
If it finds a match, and new_path is not empty, it redirects to\nnew_path using a 301 (“Moved Permanently”) redirect. You can subclass\nRedirectFallbackMiddleware\nand set\nresponse_redirect_class\nto django.http.HttpResponseRedirect to use a\n302 Moved Temporarily redirect instead.
If it finds a match, and new_path is empty, it sends a 410 (“Gone”)\nHTTP header and empty (content-less) response.
If it doesn’t find a match, the request continues to be processed as\nusual.
The middleware only gets activated for 404s – not for 500s or responses of any\nother status code.
\nNote that the order of MIDDLEWARE matters. Generally, you can put\nRedirectFallbackMiddleware at the\nend of the list, because it’s a last resort.
For more on middleware, read the middleware docs.
\nIf you’ve activated the automatic Django admin interface, you should see a\n“Redirects” section on the admin index page. Edit redirects as you edit any\nother object in the system.
\nRedirects are represented by a standard\nDjango model, which lives in\ndjango/contrib/redirects/models.py. You can access redirect\nobjects via the Django database API. For\nexample:
\n>>> from django.conf import settings\n>>> from django.contrib.redirects.models import Redirect\n>>> # Add a new redirect.\n>>> redirect = Redirect.objects.create(\n... site_id=1,\n... old_path="/contact-us/",\n... new_path="/contact/",\n... )\n>>> # Change a redirect.\n>>> redirect.new_path = "/contact-details/"\n>>> redirect.save()\n>>> redirect\n<Redirect: /contact-us/ ---> /contact-details/>\n>>> # Delete a redirect.\n>>> Redirect.objects.filter(site_id=1, old_path="/contact-us/").delete()\n(1, {'redirects.Redirect': 1})\nYou can change the HttpResponse classes used\nby the middleware by creating a subclass of\nRedirectFallbackMiddleware\nand overriding response_gone_class and/or response_redirect_class.
The HttpResponse class used when a\nRedirect is not found for the\nrequested path or has a blank new_path value.
Defaults to HttpResponseGone.
The HttpResponse class that handles the redirect.
Defaults to HttpResponsePermanentRedirect.