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
Some time ago, the ability to pass headers from a tab to a websocket client was added in the following PR: #2719
We have a similar use case, but are forced into using a legacy WS client. Is there a way of updating the toolkit to allow the headers to passed to the legacy client in the same way?
The text was updated successfully, but these errors were encountered:
Some time ago, the ability to pass headers from a tab to a websocket client was added in the following PR:
#2719
We have a similar use case, but are forced into using a legacy WS client. Is there a way of updating the toolkit to allow the headers to passed to the legacy client in the same way?
The text was updated successfully, but these errors were encountered: