Namespace does not work for socket.io-client in node.js app
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Namespace on web page client works fine for me:
// Browser side JS: processed by browserify
var io = require('socket.io-client')('/namespace');
io.emit("message", data);
Server receives connect and the message without any problem. However if I try to make client app with node.js name space does not work. Code is following:
test.js
var io = require('socket.io-client');
var socket = io.connect('http://localhost:3000', {
reconnect: true,
path: '/namespace'
});
// Add a connect listener
socket.on('connect', function(socket) {
console.log('Test connected!');
});
socket.emit('message', data);
In this case running node test.js client never connects to the server and can't emit any message. On server side console I see following output:
GET /namespace/?EIO=3&transport=polling&t=MT0IoBp&b64=1 404 22.327 ms - 1423
Any ideas? Bug or need to setup namespace in a different way?
javascript node.js socket.io
asked Nov 23 '18 at 11:23
Aleksey KontsevichAleksey Kontsevich
1,36021862
add a comment |
Namespace on web page client works fine for me:
// Browser side JS: processed by browserify
var io = require('socket.io-client')('/namespace');
io.emit("message", data);
Server receives connect and the message without any problem. However if I try to make client app with node.js name space does not work. Code is following:
test.js
var io = require('socket.io-client');
var socket = io.connect('http://localhost:3000', {
reconnect: true,
path: '/namespace'
});
// Add a connect listener
socket.on('connect', function(socket) {
console.log('Test connected!');
});
socket.emit('message', data);
In this case running node test.js client never connects to the server and can't emit any message. On server side console I see following output:
GET /namespace/?EIO=3&transport=polling&t=MT0IoBp&b64=1 404 22.327 ms - 1423
Any ideas? Bug or need to setup namespace in a different way?
javascript node.js socket.io
asked Nov 23 '18 at 11:23
Aleksey KontsevichAleksey Kontsevich
1,36021862
add a comment |
Namespace on web page client works fine for me:
// Browser side JS: processed by browserify
var io = require('socket.io-client')('/namespace');
io.emit("message", data);
Server receives connect and the message without any problem. However if I try to make client app with node.js name space does not work. Code is following:
test.js
var io = require('socket.io-client');
var socket = io.connect('http://localhost:3000', {
reconnect: true,
path: '/namespace'
});
// Add a connect listener
socket.on('connect', function(socket) {
console.log('Test connected!');
});
socket.emit('message', data);
In this case running node test.js client never connects to the server and can't emit any message. On server side console I see following output:
GET /namespace/?EIO=3&transport=polling&t=MT0IoBp&b64=1 404 22.327 ms - 1423
Any ideas? Bug or need to setup namespace in a different way?
javascript node.js socket.io
asked Nov 23 '18 at 11:23
Aleksey KontsevichAleksey Kontsevich
1,36021862
Namespace on web page client works fine for me:
// Browser side JS: processed by browserify
var io = require('socket.io-client')('/namespace');
io.emit("message", data);
Server receives connect and the message without any problem. However if I try to make client app with node.js name space does not work. Code is following:
test.js
var io = require('socket.io-client');
var socket = io.connect('http://localhost:3000', {
reconnect: true,
path: '/namespace'
});
// Add a connect listener
socket.on('connect', function(socket) {
console.log('Test connected!');
});
socket.emit('message', data);
In this case running node test.js client never connects to the server and can't emit any message. On server side console I see following output:
GET /namespace/?EIO=3&transport=polling&t=MT0IoBp&b64=1 404 22.327 ms - 1423
Any ideas? Bug or need to setup namespace in a different way?
javascript node.js socket.io
javascript node.js socket.io
asked Nov 23 '18 at 11:23
Aleksey KontsevichAleksey Kontsevich
1,36021862
asked Nov 23 '18 at 11:23
Aleksey KontsevichAleksey Kontsevich
1,36021862
asked Nov 23 '18 at 11:23
Aleksey KontsevichAleksey Kontsevich
1,36021862
asked Nov 23 '18 at 11:23
Aleksey KontsevichAleksey Kontsevich
1,36021862
asked Nov 23 '18 at 11:23
Aleksey KontsevichAleksey Kontsevich
1,36021862
1,36021862
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Changed node.js client code to
var socket = io.connect('http://localhost:3000/namespace', {
reconnect: true
});
works fine!
answered Nov 23 '18 at 11:50
Aleksey KontsevichAleksey Kontsevich
1,36021862
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445800%2fnamespace-does-not-work-for-socket-io-client-in-node-js-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Changed node.js client code to
var socket = io.connect('http://localhost:3000/namespace', {
reconnect: true
});
works fine!
answered Nov 23 '18 at 11:50
Aleksey KontsevichAleksey Kontsevich
1,36021862
add a comment |
Changed node.js client code to
var socket = io.connect('http://localhost:3000/namespace', {
reconnect: true
});
works fine!
answered Nov 23 '18 at 11:50
Aleksey KontsevichAleksey Kontsevich
1,36021862
add a comment |
Changed node.js client code to
var socket = io.connect('http://localhost:3000/namespace', {
reconnect: true
});
works fine!
answered Nov 23 '18 at 11:50
Aleksey KontsevichAleksey Kontsevich
1,36021862
Changed node.js client code to
var socket = io.connect('http://localhost:3000/namespace', {
reconnect: true
});
works fine!
answered Nov 23 '18 at 11:50
Aleksey KontsevichAleksey Kontsevich
1,36021862
answered Nov 23 '18 at 11:50
Aleksey KontsevichAleksey Kontsevich
1,36021862
answered Nov 23 '18 at 11:50
Aleksey KontsevichAleksey Kontsevich
1,36021862
answered Nov 23 '18 at 11:50
Aleksey KontsevichAleksey Kontsevich
1,36021862
1,36021862
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53445800%2fnamespace-does-not-work-for-socket-io-client-in-node-js-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
