_Bastler/partey_workadventure
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Don't retry Axios if a token decryption failed

Browse Source 
If a token decryption failed, it will emit a HTTP 500.

We should not retry Axios in this case but rather fail.

Note: a token decryption failed should not throw a HTTP 500 but another error code (HTTP 401?)
So maybe this fix is plainly wrong.
This commit is contained in:
David Négrier 2021-12-08 10:58:53 +01:00
parent 1e6ce4dec8
commit ff77a18262
2 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
front/src/Connexion/AxiosUtils.ts
View File

@ -13,6 +13,12 @@ axiosWithRetry.defaults.raxConfig = {
maxRetryAfter: 60_000, maxRetryAfter: 60_000,
statusCodesToRetry: [
[100, 199],
[429, 429],
[501, 599],
],
// You can detect when a retry is happening, and figure out how many // You can detect when a retry is happening, and figure out how many
// retry attempts have been made // retry attempts have been made
onRetryAttempt: (err) => { onRetryAttempt: (err) => {

3
messages/protos/messages.proto
View File

@ -259,6 +259,9 @@ message BanUserMessage{
string message = 2; string message = 2;
} }
/**
* Messages going from back and pusher to the front
*/
message ServerToClientMessage { message ServerToClientMessage {
oneof message { oneof message {
BatchMessage batchMessage = 1; BatchMessage batchMessage = 1;