Bug #21783
redéscendre le timeout à 3s mais permettre 3 essaies
100%
Description
Si 3 erreurs consécutives, alors afficher une page d'erreur permettant à l'utilisateur de retenter.
Files
Associated revisions
retry HTTP requests 3 times (fixes #21783)
Retry is applied to access token request and user info requests (through
OAuth2Session). There is a small exponential backoff of 0.5 and 1s.
Also decrease log level of message for failure of retrieval of the
access token or the user info to the level WARNING, that's never been a
problem for the user, as he was correctly redirected to its origin
(usually and IdP endpoint).
History
Updated by Benjamin Dauvergne almost 6 years ago
- File 0002-retry-HTTP-requests-3-times-fixes-21783.patch 0002-retry-HTTP-requests-3-times-fixes-21783.patch added
- File 0001-tox.ini-remove-python-catchlog-which-is-obsolete.patch 0001-tox.ini-remove-python-catchlog-which-is-obsolete.patch added
J'ai aussi couvert la récupération des user_info, au passage je corrige un
warning de pytest à propos de pytest-catchlog.
Updated by Benjamin Dauvergne almost 6 years ago
- File 0002-retry-HTTP-requests-3-times-fixes-21783.patch 0002-retry-HTTP-requests-3-times-fixes-21783.patch added
- File 0001-tox.ini-remove-python-catchlog-which-is-obsolete.patch 0001-tox.ini-remove-python-catchlog-which-is-obsolete.patch added
En fait on jamais vraiment eu de souci ici, l'utilisateur pouvait déjà réessayer tranquillement de s'authentifier.
Updated by Benjamin Dauvergne almost 6 years ago
- Status changed from En cours to Résolu (à déployer)
- % Done changed from 0 to 100
Appliqué par commit authentic2-auth-fc|c701e6104358c0307c2fd18895c4952cc55da092.
Updated by Benjamin Dauvergne almost 6 years ago
- Status changed from Résolu (à déployer) to Fermé
retry HTTP requests 3 times (fixes #21783)
Retry is applied to access token request and user info requests (through
OAuth2Session). There is a small exponential backoff of 0.5 and 1s.
Also decrease log level of message for failure of retrieval of the
access token or the user info to the level WARNING, that's never been a
problem for the user, as he was correctly redirected to its origin
(usually and IdP endpoint).