Upload
-
View
195
Download
0
Embed Size (px)
Citation preview
APPLICATION LAYERHTTP-HTTPS
Student: Saed Mohammed Alghamdi
Instructor: Ibrahim Alodaini
Hypertext Transfer Protocol
HTTP is a Client-Server communication model.
ClientWeb Browser
ServerWeb Server
HTTP/HTTPS
People often don’t want to remember bunch of numeric addresses and relate them with the desired websites, so the idea of giving names to websites comes to mankind.
Unfortunately, that made a gap communication wise which shed the light to creating a protocol specific to the client-server communication.
Browser recognizes three parts of (URL):http://(Protocol/scheme)
www.cisco.com(server name)Index.html(file name)
The browser then checks with (DNS) to get numeric address.
We mentioned that HTTP is a client-server model, which means it’s a request-response protocol involving a lot of messaging. So there comes the need of messaging types within the HTTP.
There are three common messaging types:1. GET. (Used when clients request data/HTML pages from
web-server).2. POST.3. PUT.
Even though HTTP is flexible, it’s NOT a secure protocol. HTTPS uses the same client request/server response process
as HTTP, BUT requires Authentication and encryption.
ConclusionThe whole purpose of Hypertext Transfer Protocol is to allow communication between web browsers and web servers smoothly and efficiently. The adds on HTTPS are Security through Authentication and encryption. There few other protocols used through out the process but we rather not make confusion listing them here.
Accept our gratitude and forgive our mistakes
Resources for this project :://https
- - . 3. . / 51static course assets s amazonaws com ITN/ / .en index html
Some figures/pictures were taken from Google.comOther detailed information are from our understanding to the content of CCNA1-CH10 : Application Layer.