Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

Question on "refreshSlack" #37

Open
t-knapp opened this issue Feb 7, 2022 · 0 comments
Open

Question on "refreshSlack" #37

t-knapp opened this issue Feb 7, 2022 · 0 comments

Comments

@t-knapp
Copy link
Contributor

t-knapp commented Feb 7, 2022

Hi,

the optional config parameter refreshSlack provides a number of seconds. This number is added to the expires in timout logic. I'm not sure what time is described by the parameter.

A.) Is it the amount of time in seconds your back-end / server is willing to accept an token that is expired?
B.) is it the amount of time in seconds that this library will use to update the token before it expires?

With the default value of 5 seconds, I face some HTTP 401 requests from time to time. The token is refreshed then and HTTP 401 is gone. It seems to me to discribe option A.) but my back-end / server does not accept expired tokens or does not care about slack.

As a workaround I use a negative refreshSlack to avoid random HTTP 401.

Kind regards,
Tobias

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant