This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using prefix on APIRouter with websockets doesn't work #2634
Comments
Solution implemented on: #2640 |
* As seen in tiangolo/fastapi#98 and tiangolo/fastapi#2634 websocket does not currently inherit the route prefix correctly, as such patch it to keep the websocket consistent with the rest of the file * Also move userID to path parameters since websockets dont support body parameters
* As seen in tiangolo/fastapi#98 and tiangolo/fastapi#2634 websocket does not currently inherit the route prefix correctly, as such patch it to keep the websocket consistent with the rest of the file * Also move userID to path parameters since websockets dont support body parameters
Thanks for the help here @Kludex ! 👏 🙇 If that solves the original problem, then you can close this issue @danrobinson88 ✔️
|
@tiangolo it does, will do, thanks. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi,
to reproduce:
This doesn't work, meaning calling the server with websocket with path /v1/calculate fail.
Whereas, it does work without prefix:
fastapi version: 0.63.0
Fixing this would be highly appreciated :)
The text was updated successfully, but these errors were encountered: