1. HTTP( Hypertext Transfer Protocol )
TRIPTI ANWITA

2. Agenda
 HTTP
 HTTP Request
 HTTP Response
 HTTP Versions
 HTTP Methods
 Status Codes
 HTTP Caching
 Session Management
 HTTP Cookies
 HTTPS
 SSL Handshake

3. HTTP
• The Hypertext Transfer Protocol (HTTP) is an application
protocol for distributed, collaborative, hypermedia
information systems.
• In use by the World-Wide Web since 1990.
• HTTP functions as a request-response protocol in the
client-server computing model

4. Need for Application Layer
Protocol

5. HTTP Request

6. HTTP Response

7. HTTP Versions
• HTTP/0.9 - The original version of HTTP was intended only for the
transfer of hypertext documents.
• HTTP/1.0 – Each Request/Response need new TCP connection
• HTTP/1.1 – Keep TCP Session. Current version in use.
• HTTP/2.0 – Future Version.

8. HTTP Methods

9. Status Codes

10. HTTP Caching
• The goal of caching is to eliminate the need to send requests in
many cases, and to eliminate the need to send full responses in
many other cases.

11. Session Management
• HTTP Protocol is stateless by design, each request is done
separately and is executed in a separate context.
• The idea behind session management is to put requests from the
same client in the same context. This is done by issuing an identifier
by the server and sending it to the client, then the client would save
this identifier and resend it in subsequent requests so the server can
identify it.

12. Session Management
• Ways to manage session –
 URL Rewriting
 Hidden Form Fields
 Cookies

13. HTTP Cookies

14. HTTPS
• The HTTPS protocol is the same text based protocol as HTTP but is
run over an encrypted SSL session.
• The Secure Sockets Layer (SSL) was designed to encrypt any
TCP/IP based network traffic and provide the following capabilities
– Prevents eavesdropping
– Prevents tampering or replaying of messages
– Uses certificates to authenticate servers and optionally clients

15. SSL Handshake