-
## Background
Combining these facts:
- Jupyter Servers (often) use API tokens for authentication
- auth tokens are typically passed in the Authorization header
- websockets cannot pass tokens …
minrk updated
4 months ago
-
It seems there is no support for adding subprotocols to a websocket request.
For Akka backend you can customize the websocket request directly to solve the issue:
```
AkkaHttpBackend(customizeW…
-
* xmpp, stomp, json, xml, ...
* (might be implemented as more robust version of encoders/decoders)
#### Affected Versions
[1.3]
-
Per https://tools.ietf.org/html/rfc6455#section-1.9, the subprotocol chosen by the server should be exposed to the client to allow negotiation of different submodules. I was trying to use AndroidAsync…
-
#828 added support for specifying subprotocols when creating a websocket, but there's no way to check which protocol the server selected.
-
## Describe the Bug
I use the `granian` HTTP Server support ASGI and get a issue below
```
File "/usr/local/lib/python3.11/site-packages/strawberry/channels/handlers/base.py", line 88, in dis…
-
When connecting to a websocket server, the client can provide multiple supported subprotocols in the header `Sec-Websocket-Protocol`. The server then chooses one of them and returns the chosen with th…
-
The socket server closes websocket connections from the graphql-ws client library:
```
File "/usr/local/lib/python3.7/site-packages/channels_graphql_ws/graphql_ws_consumer.py", line 233, in connect
…
stam updated
9 months ago
-
### Is there an existing feature request for this?
- [X] I have searched the existing feature requests
### Is your feature request related to a problem? Please describe.
I am in a situation w…
-
From the Websocket RFC6455:
For client side:
> |Sec-WebSocket-Protocol| header field, with a list of values indicating which protocols the client would like to speak, ordered by preference.
And…