seahub_django_request.log
2018-01-22 06:29:44,178 [WARNING] django.request:98 _reject Forbidden (CSRF token missing or incorrect.): /avatar/add/
2018-01-22 06:38:12,886 [WARNING] django.request:98 _reject Forbidden (CSRF token missing or incorrect.): /avatar/add/
2018-01-22 06:45:02,464 [WARNING] django.request:98 _reject Forbidden (CSRF token missing or incorrect.): /avatar/add/
seahub.log
seahub.log
2018-01-22 06:13:57,662 [ERROR] seahub.thumbnail.views:77 latest_entry [Errno 2] No such file or directory: ‘/seafile/seahub-data/thumbnail/thumb/1024/35b10f12a3bf1027e9257c2af4c06fdd90b824e2’
2018-01-22 06:13:57,823 [ERROR] seahub.thumbnail.views:77 latest_entry [Errno 2] No such file or directory: ‘/seafile/seahub-data/thumbnail/thumb/1024/18aafc496457dc8a6eb90a771e94ffab247f3b25’
2018-01-22 06:15:02,458 [ERROR] seahub.thumbnail.views:77 latest_entry [Errno 2] No such file or directory: '/seafile/seahub-data/thumbnail/thumb/1024/83e5358b79c78dc2999a04d87c3a6dc738896344
网页403错误
禁止访问 (403)
CSRF验证失败. 相应中断.
Help
Reason given for failure:
CSRF token missing or incorrect.
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 passes a request to the template’s 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.
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.