From abf599be33b383a6a5baf9493093b2126a622ac8 Mon Sep 17 00:00:00 2001
From: ttt
Date: Sat, 13 May 2017 00:29:47 +0530
Subject: added all server files
---
lib/python2.7/site-packages/django/views/csrf.py | 104 +++++++++++++++++++++++
1 file changed, 104 insertions(+)
create mode 100644 lib/python2.7/site-packages/django/views/csrf.py
(limited to 'lib/python2.7/site-packages/django/views/csrf.py')
diff --git a/lib/python2.7/site-packages/django/views/csrf.py b/lib/python2.7/site-packages/django/views/csrf.py
new file mode 100644
index 0000000..c95d19d
--- /dev/null
+++ b/lib/python2.7/site-packages/django/views/csrf.py
@@ -0,0 +1,104 @@
+from django.http import HttpResponseForbidden
+from django.template import Context, Template
+from django.conf import settings
+
+# We include the template inline since we need to be able to reliably display
+# this error message, especially for the sake of developers, and there isn't any
+# other way of making it available independent of what is in the settings file.
+
+CSRF_FAILURE_TEMPLATE = """
+
+
+
+
+
+ 403 Forbidden
+
+
+
+
+
Forbidden (403)
+
CSRF verification failed. Request aborted.
+{% if no_referer %}
+
You are seeing this message because this HTTPS site requires a 'Referer
+ header' to be sent by your Web browser, but none was sent. This header is
+ required for security reasons, to ensure that your browser is not being
+ hijacked by third parties.
+
+
If you have configured your browser to disable 'Referer' headers, please
+ re-enable them, at least for this site, or for HTTPS connections, or for
+ 'same-origin' requests.
+{% endif %}
+
+
Help
+ {% if reason %}
+
Reason given for failure:
+
+ {{ reason }}
+
+ {% endif %}
+
+
In general, this can occur when there is a genuine Cross Site Request Forgery, or when
+ Django's
+ CSRF mechanism has not been used correctly. For POST forms, you need to
+ ensure:
+
+
+ - Your browser is accepting cookies.
+
+ - The view function uses
RequestContext
+ for the template, instead of Context.
+
+ - In the template, there is a
{% templatetag openblock %} csrf_token
+ {% templatetag closeblock %} template tag inside each POST form that
+ targets an internal URL.
+
+ - If you are not using
CsrfViewMiddleware, then you must use
+ csrf_protect on any views that use the csrf_token
+ template tag, as well as those that accept the POST data.
+
+
+
+
You're seeing the help section of this page because you have DEBUG =
+ True in your Django settings file. Change that to False,
+ and only the initial error message will be displayed.
+
+
You can customize this page using the CSRF_FAILURE_VIEW setting.
+
+
More information is available with DEBUG=True.
+