Invalid namespace for socket v2 connecting to server v3 #3791
Comments
darrachequesne
added a commit
that referenced
this issue
Feb 3, 2021
In Socket.IO v2, the Socket query option was appended to the namespace
in the CONNECT packet:
{
type: 0,
nsp: "/my-namespace?abc=123"
}
Note: the "query" option on the client-side (v2) will be found in the
"auth" attribute on the server-side:
```
// client-side
const socket = io("/nsp1", {
query: {
abc: 123
}
});
socket.query = { abc: 456 };
// server-side
const io = require("socket.io")(httpServer, {
allowEIO3: true // enable compatibility mode
});
io.of("/nsp1").on("connection", (socket) => {
console.log(socket.handshake.auth); // { abc: 456 } (the Socket query)
console.log(socket.handshake.query.abc); // 123 (the Manager query)
});
More information here: https://socket.io/docs/v3/migrating-from-2-x-to-3-0/#Add-a-clear-distinction-between-the-Manager-query-option-and-the-Socket-query-option
Related: #3791
|
This should be fixed by 6f4bd7f (included in Thanks for reporting the issue! |
dzad
pushed a commit
to dzad/socket.io
that referenced
this issue
May 29, 2023
In Socket.IO v2, the Socket query option was appended to the namespace
in the CONNECT packet:
{
type: 0,
nsp: "/my-namespace?abc=123"
}
Note: the "query" option on the client-side (v2) will be found in the
"auth" attribute on the server-side:
```
// client-side
const socket = io("/nsp1", {
query: {
abc: 123
}
});
socket.query = { abc: 456 };
// server-side
const io = require("socket.io")(httpServer, {
allowEIO3: true // enable compatibility mode
});
io.of("/nsp1").on("connection", (socket) => {
console.log(socket.handshake.auth); // { abc: 456 } (the Socket query)
console.log(socket.handshake.query.abc); // 123 (the Manager query)
});
More information here: https://socket.io/docs/v3/migrating-from-2-x-to-3-0/#Add-a-clear-distinction-between-the-Manager-query-option-and-the-Socket-query-option
Related: socketio#3791
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After upgrading the server to v3.1.0 and using the
allowEIO3: trueoption the client socket v2.2.0 cannot connect to the indicated namespace anymore.The client connects to the URL
https://localhost:3700/frontend?sessionId=2053f60c072e0749d141112ddc851e00942785d7&revision=developWhen the query parameters are removed the connection to
/frontendsucceeds.Server v2.2.0 was working fine with the query parameters.
Any thoughts?
The text was updated successfully, but these errors were encountered: