# Log error: "Can't verify CSRF token authenticity"
**URL:** https://meta.discourse.org/t/log-error-cant-verify-csrf-token-authenticity/26474
**Category:** Support
**Created:** [March 18, 2015, 10:05am UTC](https://meta.discourse.org/t/log-error-cant-verify-csrf-token-authenticity/26474 "2015-03-18T10:05:33Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@vulkanino](https://meta.discourse.org/u/vulkanino)
#### Post date: [March 18, 2015, 10:05am UTC](https://meta.discourse.org/t/log-error-cant-verify-csrf-token-authenticity/26474/1 "2015-03-18T10:05:33Z")
I am receiving lots of this error in the log.
What could it be?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [March 19, 2015, 11:34pm UTC](https://meta.discourse.org/t/log-error-cant-verify-csrf-token-authenticity/26474/2 "2015-03-19T23:34:33Z")
Check the tabs at the bottom, is it for the URL /topics/timings ? This just means some kind of network error between the user and the site, as if they were on mobile and lost the signal.
@sam we should probably suppress these, as there are a lot of them.. and they are meaningless.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 19, 2015, 11:42pm UTC](https://meta.discourse.org/t/log-error-cant-verify-csrf-token-authenticity/26474/3 "2015-03-19T23:42:44Z")
Something weird is going on, we are getting CSRF issue on /posts/timing on meta which is an API we control.
Need to investigate cause the side effect of this error is that posts are not marked read.
---
### Author:  [@vulkanino](https://meta.discourse.org/u/vulkanino)
#### Post date: [March 22, 2015, 5:10pm UTC](https://meta.discourse.org/t/log-error-cant-verify-csrf-token-authenticity/26474/4 "2015-03-22T17:10:53Z")
Not sure what you mean, at the bottom I have this:
edit:
Clicking on an error, then env tab:
```
HTTP_HOST: rasando.it
REQUEST_URI: /topics/timings
REQUEST_METHOD: POST
HTTP_USER_AGENT: Mozilla/5.0 (Linux; Android 4.4.2; LG-D802 Build/KOT49I.D80220c) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36
HTTP_ACCEPT: */*
HTTP_REFERER: http://rasando.it/t/marzo-2015/327/45
HTTP_X_FORWARDED_FOR: 87.1.235.67
HTTP_X_REAL_IP: 87.1.235.67
params:
timings: null
topic_time: 3238
topic_id: 327Share Protect
```
---
### Author:  [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [March 23, 2015, 1:16am UTC](https://meta.discourse.org/t/log-error-cant-verify-csrf-token-authenticity/26474/5 "2015-03-23T01:16:14Z")
> [@sam](#):
>
> Something weird is going on, we are getting CSRF issue on /posts/timing on meta which is an API we control.
>
> Need to investigate cause the side effect of this error is that posts are not marked read.
This topic has been created before:
[https://meta.discourse.org/t/cant-verify-csrf-token-authenticity/25568?u=deanmarktaylor](https://meta.discourse.org/t/cant-verify-csrf-token-authenticity/25568)
I specifically mentioned this only occurs for mobile users for me:
[https://meta.discourse.org/t/cant-verify-csrf-token-authenticity/25568/5?u=deanmarktaylor](https://meta.discourse.org/t/cant-verify-csrf-token-authenticity/25568/5)
I’ve also updated commented on stating my thoughts on why this happens:
[https://meta.discourse.org/t/cant-verify-csrf-token-authenticity/25568/13?u=deanmarktaylor](https://meta.discourse.org/t/cant-verify-csrf-token-authenticity/25568/13)
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [March 23, 2015, 6:04am UTC](https://meta.discourse.org/t/log-error-cant-verify-csrf-token-authenticity/26474/6 "2015-03-23T06:04:04Z")