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
It would be useful if there was a method on the NodeBasedHandler to stop waiting for a response / close the server if the auth redirect flow is interrupted or cancellation request is issued
Describe the problem
If a user interrupts the auth redirect flow (closing the browser or navigating away, for example) then the authorization request never completes and the server remains waiting for a response.
Actual Behavior
There is no way to close the server
Steps to reproduce the behavior
Initiate the auth redirect, then close the browser without completing the process.
This is a valid feature request. I will add this to my backlog. You should take a look at node_support/node_request_handler.ts to enable this on your own in the meantime.
This bit us as well. It would be nice if there was a function call to abort an existing request as all the members that could allow us to do so are marked protected and inaccessible.
Expected Behavior
It would be useful if there was a method on the NodeBasedHandler to stop waiting for a response / close the server if the auth redirect flow is interrupted or cancellation request is issued
Describe the problem
If a user interrupts the auth redirect flow (closing the browser or navigating away, for example) then the authorization request never completes and the server remains waiting for a response.
Actual Behavior
There is no way to close the server
Steps to reproduce the behavior
Initiate the auth redirect, then close the browser without completing the process.
Environment
The text was updated successfully, but these errors were encountered: