[NOT BUG] csrf check faild in add new commet

[a1012112796]

• Gitea version (or commit ref): version 1.13.0+dev-735-gdf4bbcd23 built with GNU Make 4.2.1, go1.14.9 : bindata, sqlite, sqlite_unlock_notify (Build with last commit: df4bbcd)
• Git version:
• Operating system:
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

GetInvalid csrf token. when add code comment. view:

log:

[Macaron] 2020-10-06 14:59:24: Started POST /testg/test_repo/pulls/5/files/reviews/comments for 192.168.1.4
[Macaron] 2020-10-06 14:59:24: Completed POST /testg/test_repo/pulls/5/files/reviews/comments 400 Bad Request in 338.589µs
2020/10/06 14:59:24 ...s/context/context.go:332:func1() [D] Session ID: 87d1841579ba977c
2020/10/06 14:59:24 ...s/context/context.go:333:func1() [D] CSRF Token: bR_QLYCBp6bLpxZQHFc4FNzrJ4Y6MTYwMTk2NzU2NDc0ODM4NzM3NA

...

[6543]

clean cache & login -> test again

[otbutz]

clean cache & login -> test again

That's a workaround but not a solution.

[6543]

If this fix it, there is already an issue about it ...

[6543]

also interesting #11188

[a1012112796]

Sadly it's not usefull, And I found an amazing thing. The submit review is usefull which is using same csrf value..., I don't know why, test with chorm 85.0.4183.12 in ubuntu 20.04 desktop

[a1012112796]

Sorry, It's my config fault.

[otbutz]

Sorry, It's my config fault.

Could you explain?