From ffa548fb561d4e32b42566cc67a2499a5e321944 Mon Sep 17 00:00:00 2001
From: Claude Paroz <claude@2xlibre.net>
Date: Thu, 25 Dec 2014 13:56:16 +0100
Subject: [PATCH] Updated link to CSRF docs
Refs #23866.
---
django/views/csrf.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/django/views/csrf.py b/django/views/csrf.py
index 9018bd981a..a709e5fc1c 100644
--- a/django/views/csrf.py
+++ b/django/views/csrf.py
@@ -59,7 +59,7 @@ CSRF_FAILURE_TEMPLATE = """
<p>In general, this can occur when there is a genuine Cross Site Request Forgery, or when
<a
- href='https://docs.djangoproject.com/en/{{ docs_version }}/ref/contrib/csrf/#ref-contrib-csrf'>Django's
+ href="https://docs.djangoproject.com/en/{{ docs_version }}/ref/csrf/">Django's
CSRF mechanism</a> has not been used correctly. For POST forms, you need to
ensure:</p>
@@ -67,7 +67,7 @@ CSRF_FAILURE_TEMPLATE = """
<li>Your browser is accepting cookies.</li>
<li>The view function uses <a
- href='https://docs.djangoproject.com/en/{{ docs_version }}/ref/templates/api/#subclassing-context-requestcontext'><code>RequestContext</code></a>
+ href="https://docs.djangoproject.com/en/{{ docs_version }}/ref/templates/api/#subclassing-context-requestcontext"><code>RequestContext</code></a>
for the template, instead of <code>Context</code>.</li>
<li>In the template, there is a <code>{% templatetag openblock %} csrf_token