{"title":"Codex of Self","link":[{"@attributes":{"href":"https:\/\/selfcodex.com\/","rel":"alternate"}},{"@attributes":{"href":"https:\/\/selfcodex.com\/feeds\/all.atom.xml","rel":"self"}}],"id":"https:\/\/selfcodex.com\/","updated":"2016-01-30T00:00:00-08:00","entry":[{"title":"Using RedirectView in urls.py","link":{"@attributes":{"href":"https:\/\/selfcodex.com\/django-using-redirectview-in-urls-py.html","rel":"alternate"}},"updated":"2016-01-30T00:00:00-08:00","author":{"name":"Ion Scerbatiuc"},"id":"tag:selfcodex.com,2016-01-30:django-using-redirectview-in-urls-py.html","summary":"

Django's RedirectView is a generic Class-based View (or CBV for short) that is handy whenever you need to implement redirects. It's especially handy in urls.py<\/code> for simple use cases where you don't need conditional redirects or any other business logic. In this post, I will explore a few use cases where you can use the view directly in the urls.py<\/code> module.<\/p>\n

A simple example<\/h2>\n

Suppose that we are revamping some areas of our product and we decide to create the new views from scratch. We want to be able to incrementally ship the new experience, while still keeping the old one around. At the end, we want to switch over to the new experience, without affecting the customers that still use the old URLs (ie. bookmarks, links sent in marketing emails, e.t.c.)<\/p>\n

We can easily accomplish that by using RedirectView<\/code>. Here's an example.<\/p>\n

# urls.py<\/span>\nfrom<\/span> django.conf.urls<\/span> import<\/span> url<\/span>\nfrom<\/span> django.views.generic.base<\/span> import<\/span> RedirectView<\/span>\n\nfrom<\/span> myapp.views<\/span> import<\/span> NewExperienceView<\/span>\n\nurlpatterns<\/span> =<\/span> [<\/span>\n    url<\/span>(<\/span>r'^path\/$'<\/span>,<\/span>\n        RedirectView<\/span>.<\/span>as_view<\/span>(<\/span>pattern_name<\/span>=<\/span>'new-path'<\/span>,<\/span> permanent<\/span>=<\/span>True<\/span>),<\/span>\n        name<\/span>=<\/span>'path'<\/span>),<\/span>\n\n    url<\/span>(<\/span>r'^path\/new\/$'<\/span>,<\/span>\n        NewExperienceView<\/span>.<\/span>as_view<\/span>(),<\/span>\n        name<\/span>=<\/span>'new-path'<\/span>)<\/span>\n]<\/span>\n<\/pre><\/div>\n\n\n
It's as easy as that. We use RedirectView.as_view<\/code> to create a new view function that we register with the url resolver. We set the pattern_name<\/code> attribute to instruct it to redirect to that named url.<\/p>\n
Note that we also used permanent=True<\/code> to make the redirect permanent (301 Moved Permanently<\/code> instead of 302 Found<\/code>). We need this in our case, because this is a permanent switch and at some point we will remove the old URL rules. This is also a recomended practice<\/a> by the search engines.<\/p>\n
A slightly more complex example<\/h2>\n
What if our old view had required arguments encoded in the URL pattern? Will the approach presented above work?<\/p>\n
It will, but only if the new view accepts the same arguments.<\/p>\n
urlpatterns<\/span> =<\/span> [<\/span>\n    url<\/span>(<\/span>r'^path\/to\/(?P<object_slug>[\\w-]+)\/$'<\/span>,<\/span>\n        RedirectView<\/span>.<\/span>as_view<\/span>(<\/span>pattern_name<\/span>=<\/span>'new-path'<\/span>,<\/span> permanent<\/span>=<\/span>True<\/span>),<\/span>\n        name<\/span>=<\/span>'path'<\/span>),<\/span>\n\n    url<\/span>(<\/span>r'^path\/new\/(?P<object_slug>[\\w-]+)\/$'<\/span>,<\/span>\n        NewExperienceView<\/span>.<\/span>as_view<\/span>(),<\/span>\n        name<\/span>=<\/span>'new-path'<\/span>)<\/span>\n]<\/span>\n<\/pre><\/div>\n\n\n
An even more complex example<\/h2>\n
What if the new view doesn't have required arguments? In that case you can't use the above approach, or you'll get a 410 Gone<\/code> response.<\/p>\n
That's happening because RedirectView<\/code> will try to use reverse<\/code> on the provided pattern_name<\/code> passing the same URL arguments extracted from your URL pattern. If the new view doesn't have arguments, the reverse will fail and you'll get the 410 Gone<\/code> response (which is the standard Django response for a URL that is None<\/code>).<\/p>\n
How can we fix that? We can set the url<\/code> directly and use reverse_lazy<\/code> to get the actual URL of the new view.<\/p>\n
# urls.py<\/span>\nfrom<\/span> django.conf.urls<\/span> import<\/span> url<\/span>\nfrom<\/span> django.core.urlresolvers<\/span> import<\/span> reverse_lazy<\/span>\nfrom<\/span> django.views.generic.base<\/span> import<\/span> RedirectView<\/span>\n\nfrom<\/span> myapp.views<\/span> import<\/span> NewExperienceView<\/span>\n\nurlpatterns<\/span> =<\/span> [<\/span>\n    url<\/span>(<\/span>r'^path\/to\/(?P<object_slug>[\\w-]+)\/$'<\/span>,<\/span>\n        RedirectView<\/span>.<\/span>as_view<\/span>(<\/span>url<\/span>=<\/span>reverse_lazy<\/span>(<\/span>'new-path'<\/span>),<\/span> permanent<\/span>=<\/span>True<\/span>),<\/span>\n        name<\/span>=<\/span>'path-to-object-slug'<\/span>),<\/span>\n\n    url<\/span>(<\/span>r'^path\/new\/$'<\/span>,<\/span>\n        NewExperienceView<\/span>.<\/span>as_view<\/span>(),<\/span>\n        name<\/span>=<\/span>'new-path'<\/span>)<\/span>\n]<\/span>\n<\/pre><\/div>\n\n\n
Other use cases<\/h2>\n
For any other use cases you most probably won't be able to use the RedirectView.as_view<\/code> directly. Here are a few examples:<\/p>\n
We used reverse_lazy<\/a> to get the actual URL for the new view and set that as the url<\/code> attribute on the RedirectView. If url<\/code> is set, RedirectView<\/code> will not do a reverse, but instead will try to do a dictionary-style string formatting, passing any arguments that where captured in the URL. In our case, the URL doesn't have any string formatting arguments, so it will remain as it is and the redirect will be handled correctly.<\/p>\n