Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Using namespace will ignore port, or default to port 80

See original GitHub issue

What’s wrong:

I have the socket.io service running on port 4040 (for example), which exposes namespace /chat. From the client side, if I try to connect to the namespace without specifying the full url, the window url will be used without the port (or default to port 80).

What works:

From the client side, connecting to the default namespace is still okay, e.g. io.connect() or io() will correctly connect with the full url 192.168.0.149:4040. Needless to say the full url works.

Repro Code

# app.coffee
express = require 'express'
io = require 'socket.io'
http = require 'http'
app = express()
server = http.createServer(app)
io = io.listen server

server.listen 4040

app.use(express.static "#{__dirname}/public")

chat = io.of 'chat'

chat.on 'connection', (socket) ->
  socket.emit 'welcome', 'howdy'

# index.html
<!DOCTYPE html>
<html>
  <head>
    <title>Chat with port demo</title>
  </head>
  <body>
    <h1>Chat ip demo</h1>
    <script src="/socket.io/socket.io.js"></script>
    <script>
      var socket = io('/chat');
      socket.once('welcome', function (message) {
        console.log(message);
      });
    </script>
  </body>
</html>

# package.json
{
  "name": "socdemo",
  "version": "1.0.0",
  "description": "",
  "main": "app.coffee",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "express": "^4.11.2",
    "socket.io": "^1.3.2"
  }
}

# error (misleading error since it's because there is nothing running on 192.168.0.149:80)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://192.168.0.149/socket.io/?EIO=3&transport=polling&t=1422967677888-0. This can be fixed by moving the resource to the same domain or enabling CORS.