Replies: 1 comment
-
|
Hi @kaaax0815! I'm Dosu and I’m helping the openapi-ts team. Yes, you can prevent recursive interceptor triggering by marking your refresh token request with a custom property or header, then checking for that marker in your interceptor.
This approach avoids relying on the URL and works across different client types. If you want a code example tailored to your specific client, let me know which one you're using! To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am sending a request from inside a interceptor (to refresh auth token). If the Refresh Token is not valid I get a 401, which in turn triggers the interceptor again.
I could exclude the request by the url, but I don't want to do that.
Is there a way to add a property to the Request before it goes through the interceptors?
Beta Was this translation helpful? Give feedback.
All reactions