This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Websocket Route Not Working With Nested Router #4930
Labels
You can continue the conversation there. Go to discussion →
First Check
Commit to Help
Example Code
Description
When upgrading from FastaAPI 0.72.0 to 0.78.0, noticed that a websocket path I had defined on a router included by another router was no longer available (server returns 403, trace logs indicate normal closure, think this is the normal behaviour when a websocket tries to upgrade a non-existent route).
Looks like #2640 fixed the case for a websocket defined on a router, but seems like the nested router makes this appear again.
Operating System
macOS
Operating System Details
FastAPI Version
0.78.8
Python Version
3.10.1
Additional Context
It's kinda weird that it did work before, since #98 would indicate that it's been a long standing problem. 🤷
The text was updated successfully, but these errors were encountered: