-
December 12th, 2012, 08:38 PM
#1
Why are there predefined application specific ports?
Why are there predefined application specific ports? for example, why is HTTP associated with port 80?
-
December 13th, 2012, 02:15 PM
#2
Re: Why are there predefined application specific ports?
It's easier since you don't have to remember what port to use as well as the url. In some way it's just like that you don't have to use the long distance prefix when you dial a local phone number.
-
June 7th, 2013, 08:48 PM
#3
Re: Why are there predefined application specific ports?
Originally Posted by maybnxtseasn
why is HTTP associated with port 80?
So you know which port to connect to on the remote computer. Without ports, the remote computer has no idea what to do when a connection is made. With a port, the computer sees a connection on port 80, says, "aha!", and activates the web server to handle it.
The reason it is 80 is because of an arbitrary list that was made back in the early 70s to handle standard requests. This list is still maintained and users can register specific ports. We are up around 13000 now for specifically registered ports, I believe.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|