Ray, When you browse to http://www.google.com/, it is actually going to http://www.google.com:80/ -- the port 80 is the default for http, it's implied if you don't specify a number.
So all you need to do is serve on port 80 and then the end user won't need to type a port number. A lot of times on production setups there is a front-door kind of server that handles traffic coming in on port 80 (or 443, which is the default for 443) and figures out what other app or server needs to handle that particular traffic (based on the subdomain or the path or whatnot) and proxies the request to the port that the appropriate server is running on. That way you can have different servers running on different ports behind the scenes, but all traffic interfacing with the public going over port 80. But if you have a simple setup, you can just serve on port 80 and have everything go through your one server. For a lot of hosting setups (like Nodejitsu) you can serve on whatever port you want and their load balancer redirects port 80 traffic to your process. -- peter -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/200b8a8c-2fde-4489-9fb2-50a4670e6e4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
