You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was pondering on how to make this middleware apply the ttl parameter differently depending on which path was provided.
Is the best way to do this by leaving the library's ttl option null and instead adding a before callable which re-decodes the token to extract the timestamp?
I was thinking if it would be feasible to run through an array of callables if the ttl option was specified like that in a similar manner to the rules, but I'm not sure how effective that would be either.
The text was updated successfully, but these errors were encountered:
Some frameworks allow you to attach middleware to specific routes or routegroups. So you could create two (or more) instances of the middleware with different ttl settings and then attachs these to different routes.
I was pondering on how to make this middleware apply the ttl parameter differently depending on which path was provided.
Is the best way to do this by leaving the library's
ttl
option null and instead adding abefore
callable which re-decodes the token to extract the timestamp?I was thinking if it would be feasible to run through an array of callables if the ttl option was specified like that in a similar manner to the rules, but I'm not sure how effective that would be either.
The text was updated successfully, but these errors were encountered: