I hate to be nitpicking but the protocol, while related to the port is still a separate thing. For example, using a url of the type ftp:// is much more than jus

I hate to be nitpicking but the protocol, while related to the port is still a separate thing. For example, using a url of the type ftp:// is much more than just switching to port 23, even worse a url of the type file:// is not bound to a port as far as I know. Switching protocols mean the actual exhange is completely different. You can actually use the http protocol on ports other than 80 and its actually commonly done on local development servers where anything like 8080, 8000, 8090 or many others are frquently used. In such a case the url would be something like http://myserver.com:8080/blabla http://myserver.com:8080/blabla where 8080 would be the port. The confusion might arise because protocols have a default port associated with them. Sorry for the explanation of something thats probably waaaay too simple for most of the readers but that comment was just so wrong for me.