yinan-c / RSSbrew

Self-hosted, easy-to-deploy RSS tool - Aggregate, filter, digest and AI summarize articles in RSS feeds.
GNU Affero General Public License v3.0
161 stars 15 forks source link

Bug report #5

Open Fan-Bob opened 5 months ago

Fan-Bob commented 5 months ago

Forbidden (403)

CSRF verification failed. Request aborted.

Help

Reason given for failure:

Origin checking failed - https://xxx.xyz 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.

yinan-c commented 4 months ago

把域名作为 DEPLOYMENT_URL 添加到 .env 文件中应该可以解决