Project:
| View Revisions: Issue #47888 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0047888: checkServerAvailability does not fail even if the session is corrupted | ||
| Revision | 2021-10-20 06:57 by alostale | ||
| Steps To Reproduce | Although it is unclear why the session got corrupted, this is part of a sequence of requests seen in an actual customer (attached the full sequence of requests received for that session): 1. 19:04 - 19:12 regular activity 2. 19:12:14 AppCacheManifest 200 -> reload page? Might the session be corrupted after this one 3. 19:21:09 ProcessCashClose 401 -> the request is sent without csrf token which makes the validation fail which makes the pos to go offline 4. checkServerAvailability every 10s 200 -> 3 successful requests make pos to go online 5. ProcessCashClose 401 -> actual request fails again so pos is offline again 6. repeats steps 4 and 5 |
||
| Revision | 2021-10-20 06:57 by alostale | ||
| Steps To Reproduce | Although it is unclear why the session got corrupted, this is part of a sequence of requests seen in an actual customer: 1. 19:04 - 19:12 regular activity 2. 19:12:14 AppCacheManifest 200 -> reload page? Might the session be corrupted after this one 3. 19:21:09 ProcessCashClose 401 -> the request is sent without csrf token which makes the validation fail which makes the pos to go offline 4. checkServerAvailability every 10s 200 -> 3 successful requests make pos to go online 5. ProcessCashClose 401 -> actual request fails again so pos is offline again 6. repeats steps 4 and 5 |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |