Not sure if this is a gogs or gogs-sandstorm problem, but when I try to apload a small attachment to an issue, it first seems to succeed, but when I hover the image i see the error
Bad Request: no CSRF token present
in the grain log I can see the following:
[Macaron] 2016-06-18 12:45:49: Started POST /issues/attachments for 127.0.0.1
2016/06/18 12:45:49 [D] Session ID: a5876b8ae94f45f9
2016/06/18 12:45:49 [D] CSRF Token: _tteyck6utej7Z9qetP3dA7rq146MTQ2NjI1Mzk0MTU3NTk2MzE3Mw==
[Macaron] 2016-06-18 12:45:49: Completed /issues/attachments 400 Bad Request in 1.102108ms
Checking the post in chrome developer tools, I can see that the request header contains the X-Csrf-Token could it be that my nginx instance is removing it? but it shows up in the logs ... strange, any ideas?
Not sure if this is a gogs or gogs-sandstorm problem, but when I try to apload a small attachment to an issue, it first seems to succeed, but when I hover the image i see the error
in the grain log I can see the following:
Checking the post in chrome developer tools, I can see that the request header contains the X-Csrf-Token could it be that my nginx instance is removing it? but it shows up in the logs ... strange, any ideas?