Django 1.1's csrf protection appears to be handled in the middleware component.

[htsworkflow.git] / htsworkflow / frontend / templates / registration / login.html

diff --git a/htsworkflow/frontend/templates/registration/login.html b/htsworkflow/frontend/templates/registration/login.html
index 1e4633717aec40066e03b18788e0c614b5e0b9c2..1f053df6e6538c96311fb1afb11b8be56b6e109b 100644 (file)
--- 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>