A quick and neat definition for TDP/UDP and HTTP/FTP

For those confusing times, I thought this was a pretty neat way of actually describing it.

TCP/IP is a big chapter and one that can’t be analyzed in a few paragraphs. To help you get the big picture, we’ll keep things simple and focus on the details you need, to ensure you get a proper understanding.

The term “TCP/IP” stands for Transmission Control Protocol / Internet Protocol and refers to a number of protocols. The “IP” part of the term, which stands for Internet Protocol, is used by TCP and UDP, to transport them from one network to another. Think of IP as a sort of high-way that allows other protocols to get on and find their way to other computers. TCP and UDP are the “trucks” on the highway, and the “load” they are carrying are protocols such as HTTP, File Transfer Protocol (FTP) and more.

As you can understand, TCP and UDP are transport

This and more can be learnt from here.

Whats the difference between http and https?

In many ways, https is identical to http, because it follows the same basic protocols. The http or https client, such as a Web browser, establishes a connection to a server on a standard port. When a server receives a request, it returns a status and a message, which may contain the requested information or indicate an error if part of the process malfunctioned. Both systems use the same Uniform Resource Identifier (URI) scheme, so that resources can be universally identified. Use of https in a URI scheme rather than http indicates that an encrypted connection is desired.

There are some primary differences between http and https, however, beginning with the default port, which is 80 for http and 443 for https. Https works by transmitting normal http interactions through an encrypted system, so that in theory, the information cannot be accessed by any party other than the client and end server. There are two common types of encryption layers: Transport Layer Security (TLS) and Secure Sockets Layer (SSL), both of which encode the data records being exchanged.

When using an https connection, the server responds to the initial connection by offering a list of encryption methods it supports. In response, the client selects a connection method, and the client and server exchange certificates to authenticate their identities. After this is done, both parties exchange the encrypted information after ensuring that both are using the same key, and the connection is closed. In order to host https connections, a server must have a public key certificate, which embeds key information with a verification of the key owner’s identity. Most certificates are verified by a third party so that clients are assured that the key is secure.

This and more information can be found here.


One thought on “A quick and neat definition for TDP/UDP and HTTP/FTP

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s