Andy Salnikov
2018-06-08 15:42:16 UTC
Hi, I have just upgraded to 3.0.2 in virtualenv setup. Now all update
operations (new document, new cabinet, new tag) fail with "CSRF
verification failed" error (below). Does anyone see it or know how to fix
this?
The browser is latest Chrome running on Windows 10, cookies are enabled,
and it worked fine with mayan 2.7.3 right before update.
CSRF verification failed. Request aborted.
Help
Reason given for failure:
Referer checking failed - Referer is malformed.
In general, this can occur when there is a genuine Cross Site Request
Forgery, or when Django's CSRF mechanism
<https://docs.djangoproject.com/en/1.11/ref/csrf/> has not been used
correctly. For POST forms, you need to ensure:
- Your browser is accepting cookies.
- The view function passes a request to the template's render
<https://docs.djangoproject.com/en/dev/topics/templates/#django.template.backends.base.Template.render>
method.
- In the template, there is a {% csrf_token %} 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.
- The form has a valid CSRF token. After logging in in another browser
tab or hitting the back button after a login, you may need to reload the
page with the form, because the token is rotated after a login.
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.
operations (new document, new cabinet, new tag) fail with "CSRF
verification failed" error (below). Does anyone see it or know how to fix
this?
The browser is latest Chrome running on Windows 10, cookies are enabled,
and it worked fine with mayan 2.7.3 right before update.
CSRF verification failed. Request aborted.
Help
Reason given for failure:
Referer checking failed - Referer is malformed.
In general, this can occur when there is a genuine Cross Site Request
Forgery, or when Django's CSRF mechanism
<https://docs.djangoproject.com/en/1.11/ref/csrf/> has not been used
correctly. For POST forms, you need to ensure:
- Your browser is accepting cookies.
- The view function passes a request to the template's render
<https://docs.djangoproject.com/en/dev/topics/templates/#django.template.backends.base.Template.render>
method.
- In the template, there is a {% csrf_token %} 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.
- The form has a valid CSRF token. After logging in in another browser
tab or hitting the back button after a login, you may need to reload the
page with the form, because the token is rotated after a login.
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.
--
---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.