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 use cases require changing the url and/or websocket connection payload. Should we add that part of the request pipeline, same as we have "HTTP headers"?
The text was updated successfully, but these errors were encountered:
I've encountered the same issue while trying to change the URL
Has there been any feature released recently that addresses this need?
martinbonnin
changed the title
[runtime] allow changing the url and/or websocket connection payload
[runtime] allow changing the url and/or websocket connection payload of experimental websockets
Feb 19, 2025
You can use the regular WebSocketNetworkTransport and serverUrl {} for this. serverUrl {} takes a lambda as parameter that will be called so you can update the url if needed.
Description
See #5862 (comment)
Some use cases require changing the url and/or websocket connection payload. Should we add that part of the request pipeline, same as we have "HTTP headers"?
The text was updated successfully, but these errors were encountered: