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
{{ message }}
This repository has been archived by the owner on Feb 16, 2023. It is now read-only.
Hi, currently, the only way to authenticate a WebSocket connection is to send the sessionid cookie to the server.
As far as I've seen token or basic authentication is not possible.
I'm currently writing an app and I'm trying to visualize the consumer status on document upload to allow the user to directly edit the previously uploaded document once consumption has finished. I would like to do this without using "ugly" long-polling to the
endpoint /api/documents/?query={{filename}} until the document has been consumed and the result is not empty.
Do you think this is something that could be implemented without sacrificing security?
Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, currently, the only way to authenticate a WebSocket connection is to send the sessionid cookie to the server.
As far as I've seen token or basic authentication is not possible.
I'm currently writing an app and I'm trying to visualize the consumer status on document upload to allow the user to directly edit the previously uploaded document once consumption has finished. I would like to do this without using "ugly" long-polling to the
endpoint /api/documents/?query={{filename}} until the document has been consumed and the result is not empty.
Do you think this is something that could be implemented without sacrificing security?
Thanks!
The text was updated successfully, but these errors were encountered: