-
-
Notifications
You must be signed in to change notification settings - Fork 295
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
Channels aren't working anymore with socket.io-client #892
Comments
+1 Something about the routing seems broken here. Really just seems like Axum didnt register that /socket.io/ path and just returns the fallback which of course leads to an error. Edit: Removing the Fallback or even disabling static sadly dosent fix the issue either |
@jondot Making sure this isnt overseen because it seems to be an actual bug. From what i can tell it started from V0.8. I even have the assumption its this commit here: dbea6b1 The chatroom example also stops compiling from that version on.
i managed to make it compile by wrapping the RwLock with an Arc. and giving the MessageStore the Clone derive but now you cant connect to it anymore. |
Any Update or workaround on this? I'm hoping to use channels |
Sorry for tagging again @kaplanelad @jondot but can we get some info about this? |
Hey @Sillyvan, |
After reviewing our implementation of You can see a working example of char-room implementation based on |
Description
The
channels
feature is not working with the most recent loco-rsv0.10.1
version and socketioxidev0.14.0
as presented in the documentation and/or in the chat-rooms example.To Reproduce
I git cloned the chat-rooms example repository and updated the both dependencies to reproduce the recent setup by updating the dependencies:
git clone https://github.com/loco-rs/chat-rooms.git cd chat-rooms
src/app.rs
file:src/bin/main.rs
:src/channels/state.rs
by adding thisClone
implementation:Expected Behavior
The messages aren't transmitted through websocket as the frontend can't connect to the backend anymore.
It seems that some url parameters have been added to the uri path when looking at the logs
I'm not sure how we could update the backend to accept the connection and allow this:
http.uri=/socket.io/?EIO=4&transport=polling&t=PApG1h6
The text was updated successfully, but these errors were encountered: