From: Diane Trout <diane@caltech.edu>
Date: Thu, 8 Sep 2011 22:22:56 +0000 (-0700)
Subject: Django 1.1's csrf protection appears to be handled in the middleware component.
X-Git-Tag: 0.5.3
X-Git-Url: http://woldlab.caltech.edu/gitweb/?p=htsworkflow.git;a=commitdiff_plain;h=90b18005d13c0fc79aae49bd8da94a8d0458b5ee;hp=39dea5abfab1e5404e9725a596dc675ad106fb90

Django 1.1's csrf protection appears to be handled in the middleware component.
So remove the csrf_token tag until we upgrade
---

diff --git a/htsworkflow/frontend/templates/registration/login.html b/htsworkflow/frontend/templates/registration/login.html
index 1e46337..1f053df 100644
--- a/htsworkflow/frontend/templates/registration/login.html
+++ b/htsworkflow/frontend/templates/registration/login.html
@@ -15,7 +15,7 @@
 {% endif %}
 <div id="container">
     <h1>Login</h1>
-<form action="{{ app_path }}" method="post" id="login-form">{% csrf_token %}
+<form action="{{ app_path }}" method="post" id="login-form">
   <div class="form-row">
     <label for="id_username">{% trans 'Username:' %}</label> <input type="text" name="username" id="id_username" />
   </div>