diff options
| author | Andrew Clayton <a.clayton@nginx.com> | 2025-01-27 16:48:41 +0000 |
|---|---|---|
| committer | Andrew Clayton <a.clayton@nginx.com> | 2025-02-03 19:06:50 +0000 |
| commit | c2279c0df85a7de23ba5def143ee8f367d599b4d (patch) | |
| tree | f9b82c293612127634cfbe36e1d327e89908be5b /src/java/nginx | |
| parent | 150378224f1d8b4e58765ce586c27f2fd36e47f0 (diff) | |
| download | unit-c2279c0df85a7de23ba5def143ee8f367d599b4d.tar.gz unit-c2279c0df85a7de23ba5def143ee8f367d599b4d.tar.bz2 | |
python: Fix Litestar WebSockets compatibility
It was reported on GitHub that Unit was unable to work with WebSockets
under Litestar Python applications.
This was due to Unit sending a 'method' variable in the WebSocket's
connection scope, which Litestar was interpreting as being a normal HTTP
connection.
The ASGI WebSocket specification makes no mention about setting a
'method', so let's not send it on WebSockets.
Also tested this change with basic ASGI WebSockets and FastAPI
WebSockets and obviously pytests still pass.
Closes: https://github.com/nginx/unit/issues/1507
Link: <https://asgi.readthedocs.io/en/latest/specs/www.html#websocket-connection-scope>
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
Diffstat (limited to 'src/java/nginx')
0 files changed, 0 insertions, 0 deletions