-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http interception promise resolves when calling controller.halt() #42990
Comments
Pinging @elastic/kibana-platform |
/cc @eliperelman |
@kobelb would you happen to have any patch for this as well? We have a test for this, but I would like to find out why this isn't being caught.
|
The promise that is returned by
|
I'm confused by your statement. This should be rejecting, correct? |
Unfortunately, no... We don't want the promise to reject, we just want it to "stall out". We're changing We're essentially trying to emulate the following within the context of a http interceptor: kibana/x-pack/legacy/plugins/security/public/services/auto_logout.js Lines 14 to 15 in 142897f
kibana/src/legacy/ui/public/promises/promises.js Lines 84 to 89 in 142897f
|
When calling
halt
on an instance of the HttpInterceptController, the promise that is returned from thehttp.fetch
resolves. This is potentially problematic for security's usage of http interception, because we wish to intercept specific401
s and redirect the user to the logout page. The old approach used Promise.halt() to accomplish this, which I thoughtHttpInterceptController
'shalt
was supposed to do as well.The text was updated successfully, but these errors were encountered: