Mojito started on http://127.0.0.1:8666/ #1043

Closed
rwaldura opened this Issue Mar 21, 2013 · 3 comments

2 participants

@rwaldura

@isao who's working on the CLI

@isao

mojito's underlying express/connect/node http server is started without specifying a host, and afaict mojito ends up listening to "connections directed to any IPv4 address (INADDR_ANY)." link

OMM:

% netstat -an | grep 8666
tcp4       0      0  127.0.0.1.8666         127.0.0.1.60749        ESTABLISHED
tcp4       0      0  127.0.0.1.60749        127.0.0.1.8666         ESTABLISHED
tcp4       0      0  127.0.0.1.8666         127.0.0.1.60746        ESTABLISHED
tcp4       0      0  127.0.0.1.60746        127.0.0.1.8666         ESTABLISHED
tcp4       0      0  127.0.0.1.8666         127.0.0.1.60745        ESTABLISHED
tcp4       0      0  127.0.0.1.60745        127.0.0.1.8666         ESTABLISHED
tcp4       0      0  *.8666                 *.*                    LISTEN   

... bout http://0.0.0.0:8666 also works

@isao isao closed this Apr 4, 2013
@rwaldura

@isao you're entirely correct.
Let's change the startup message to "Mojito started on on port 8666" because that's what it does.

@rwaldura rwaldura reopened this Apr 5, 2013
@isao isao was assigned Apr 5, 2013
@isao isao added a commit that closed this issue Apr 6, 2013
@isao isao reword start msg. fixes #1043
mojito's underlying express/connect/node http server is started without specifying a host, and ends up listening to "connections directed to any IPv4 address (INADDR_ANY)." http://y.ahoo.it/XO3S2 see alse http://y.ahoo.it/dIdNP
13df1f3
@isao isao closed this in 13df1f3 Apr 6, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment