Project:
View Revisions: Issue #46814 | [ Back to Issue ] | ||
Summary | 0046814: JIRA 1730 - TerminalLogLoader - Error 401 | ||
Revision | 2021-05-25 12:16 by gorka_gil | ||
Description | On the POS, we have in console/network a 401 error on TerminalLogLoader Request URL: https://agapes-test.cloud.openbravo.com/openbravo/org.openbravo.mobile.core.service.jsonrest/org.openbravo.mobile.core.TerminalLogLoader?$timeout=15000 [^] Request Method: POST Status Code: 401 401 Response: {"response":{"status":-1,"error":{"message":"Request CSRF Token does not match with the one provided by Session","messageType":"Error","title":""},"totalRows":0}} EDIT ggi: * Summary: Most probably the problem is related to the synchronization buffer starting to soon. * Details: When the login finish it is saved the csrf token, that is needed for all the requests to backend to work. Looks like the synchronization buffer is trying to start sending messages to backend when we still don't have this csrf token. It fails with the terminal log messages because they are the most common messages, also are generated while logout and when user is doing login, so is common to have terminal log messages waiting that the synchronization buffer starts after login to start synchronizing them * Proposed fix: Delay the start of the synchronization buffer till we have the csrf token. |
||
Revision | 2021-05-25 12:11 by gorka_gil | ||
Description | On the POS, we have in console/network a 401 error on TerminalLogLoader Request URL: https://agapes-test.cloud.openbravo.com/openbravo/org.openbravo.mobile.core.service.jsonrest/org.openbravo.mobile.core.TerminalLogLoader?$timeout=15000 [^] Request Method: POST Status Code: 401 401 Response: {"response":{"status":-1,"error":{"message":"Request CSRF Token does not match with the one provided by Session","messageType":"Error","title":""},"totalRows":0}} |
Copyright © 2000 - 2009 MantisBT Group |