Replies: 1 comment
-
It's difficult to pinpoint where the delay is coming from as there are many potential culprits here:
What we can rule out, is the token refresh reason: unless the client is configured to have a very short token lifetime, the BFF will not refresh the token on every request. Tokens will only be refreshed when the access token is nearing its expiration time. When you say "one of my sites" and "I have wrapped my config in a component so the setup should be the same as my other sites (which don't experience this).", does this mean that you only use the wrapped config logic in this application? If so, I would recommend to temporarily switch to statically configuring the app, to rule out that the custom logic is causing the delay. Furthermore, I would enable additional logging for the following namespaces on the
You may need to doublecheck your log configuration to ensure that the logged timestamps are showing milliseconds.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
One of my sites experiences delays when making API requests through the BFF Proxy. I have wrapped my config in a component so the setup should be the same as my other sites (which don't experience this).
The key difference is likely to be configuration and I'm wondering if the delay (somewhere around 6 seconds when running on a server, its much better locally) could be due to BFF refreshing the token before each request?
Can somebody please let me know if there are any likely culprits, or anything I can do to provide additional logging from the BFF Proxy provider.
Let me know if you need any code examples to support this. Thanks!
[React front end, BFF in a dotnet backend.]
Beta Was this translation helpful? Give feedback.
All reactions