侧边栏壁纸
博主头像
进一步,海阔天空 博主等级

进一步,海阔天空

  • 累计撰写 165 篇文章
  • 累计创建 19 个标签
  • 累计收到 7 条评论

目 录CONTENT

文章目录

seafile升级到v11.x后出现403错误的解决办法

Kevin Meng
2024-01-20 / 0 评论 / 0 点赞 / 26 阅读 / 0 字

最近把seafile服务升级到了11版本,但是登录后出现如下错误:

Forbidden (403)

CSRF verification failed. Request aborted.

首先修改/conf/seahub_settings.py,加入DEBUG = True,看看是什么错误。打开后重启seafile的docker容器,再次访问出现如下提示:

Help

Reason given for failure:

    Origin checking failed - http://xxx.com does not match any trusted origins.
    

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.

  • 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.

修改/conf/seahub_settings.py,加入如下配置即可:

CSRF_TRUSTED_ORIGINS = ["http://xxx.com"]

0

评论区