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
@wms2537 thanks for pointing this our, I'll propose a backwards compatible change by allowing in an upcoming change and rollout that you can specify the location property in the following three flavors:
<location> which get's pre-fixed and post-fixed to ws://<location>/rpc
ws://<location> which get's post-fixed to ws://<location>/rpc
wss://<location> which get's post-fixed to wss://<location>/rpc
I wonder why is the protocol
ws
being hardcoded. For servers which require wss, it results in awebsocket: bad handshake
error.https://github.com/fiskaly/grafana.surrealdb/blob/f1681f35603219b882e10dd76c70aed9ef81d26b/pkg/plugin/datasource.go#L97C2-L97C57
The text was updated successfully, but these errors were encountered: