HTTP and web service: A Deep Dive into Application Layer Protocols
- 1. DEPARTMENT OF INFORMATION TECHNOLOGY SUBJECT :COMPUTER NETWORKS SUBJECT CODE : 191ITC501T SUBJECT HANDLER :Mrs.S. Shereen Priscila TOPIC: HTTP and Web Services: A Deep Dive into Application Layer Protocols TEAM MEMBERS
- 2. CONTENTS • Introduction • Hyper Text Transfer Protocol • Working of http • Http methods • Web services- Restful web services,SOAP web services • Http vs Https • Http status codes • Security in http and web services
- 3. INTRODUCTION • Application Layer Protocols enable communication between software applications across networks. • They define rules for how data is sent and received by applications. • Examples include: HTTP (HyperText Transfer Protocol) – for web communication FTP (File Transfer Protocol) – for transferring files SMTP (Simple Mail Transfer Protocol) – for sending emails
- 4. HYPERTEXT TRANSFER PROTOCOL • HTTP (HyperText Transfer Protocol) is the foundation of data communication on the web. • It’s used for transmitting web pages, images, videos, and other resources over the internet. KEY FEATURES: 1. Stateless Protocol: Each request is independent; the server doesn't remember previous interactions. 2. Client-Server Architecture: The client (e.g., web browser) sends requests, and the server responds. 3. Request-Response Model: The client sends an HTTP request, and the server sends back an HTTP response.
- 5. WORKING OF HTTP Client-Server Communication: 1. Client sends an HTTP request. 2. Server processes the request. 3. Server sends back an HTTP response. Key Components: URL: Specifies the resource being requested. HTTP Methods: Defines the action (GET, POST, etc.). Headers: Provide extra information (e.g., content type). Body (Optional): Contains data in requests (e.g., form data in POST) or responses. Request-Response Cycle: Central to how web pages and APIs function.
- 6. HTTP METHODS • GET: Retrieve data from the server (e.g., viewing a webpage). • POST: Send data to the server to create a new resource (e.g., submitting a form). • PUT: Update an existing resource completely (e.g., updating a user profile). • DELETE: Remove a resource from the server (e.g., deleting a user account). • PATCH: Update parts of a resource (e.g., modifying specific fields). Each HTTP method corresponds to a specific action, enabling communication between clients and servers.
- 7. WEB SERVICES Enable communication between different applications over the internet. Types of Web Services: • REST (Representational State Transfer):Lightweight, uses HTTP methods.Works with various data formats (JSON, XML).Focuses on resources (e.g., GET /users/123 to retrieve user data). • SOAP (Simple Object Access Protocol): XML-based protocol for exchanging information.Heavier, more structured compared to REST. Often used in enterprise applications with complex security requirements.Web services are essential for connecting mobile apps, websites, and backend systems.
- 8. RESTful Web Services • REST (Representational State Transfer) is an architectural style for designing networked applications. ADVANTAGES: • Simplicity:Easy to use and understand. • Scalability:Well-suited for modern web and mobile applications. • Flexibility:Supports multiple data formats (JSON, XML, etc.). • Widely Adopted:Common in public APIs (e.g., Twitter, Google Maps). Example: GET/users/123 Retrieves information about a specific user in JSON format.
- 9. SOAP web services • SOAP (Simple Object Access Protocol) is a protocol for exchanging structured information in web services. KEY FEATURES: XML-Based: SOAP messages are always formatted in XML. Protocol-Independent: Can be used over various protocols (HTTP, SMTP, etc.). WSDL (Web Services Description Language): Describes the services offered and how to access them. • Standardized:Well-defined standards for security (WS-Security) and transactions. • Reliability:Supports ACID-compliant transactions. • Interoperability:Works across different platforms and languages. ADVANTAGES:
- 10. HTTP VS HTTPS HTTP (HyperText Transfer Protocol) • Protocol for transferring data over the web without encryption. • Data is transmitted in plain text, making it vulnerable to interception. • Suitable for non-sensitive information (e.g., public websites) HTTPS (HyperText Transfer ProtocolSecure) • Extension of HTTP that adds a layer of security using SSL/TLS encryption. • Encrypts data during transmission, protecting it from eavesdropping and tampering. • Essential for websites handling sensitive information (e.g., online banking, e-commerce).
- 11. HTTP STATUS CODES 2xx - Success: • 200 OK: Request was successful. • 201 Created: Resource created successfully. • 204 No Content: Successful request with no content to return. 3xx - Redirection: • 301 Moved Permanently: Resource has been permanently moved to a new URL. • 302 Found: Resource is temporarily located at a different URL. 4xx - Client Error: • 400 Bad Request: Invalid syntax in the request. • 401 Unauthorized: Authentication required, failed, o not provided. • 404 Not Found: Resource could not be found on the server. 5xx - Server Error: • 500 Internal Server Error: Unexpected server condition. • 503 Service Unavailable: Server is not ready to handle the request.
- 12. SECURITY IN HTTP AND WEB SERVICES Importance of Security: • Protects sensitive data during transmission. • Ensures confidentiality, integrity, and authenticity. Security Measures: HTTPS:Uses SSL/TLS encryption to secure data, preventing eavesdropping and attacks. Authentication Mechanisms: Basic Authentication: Encodes user credentials; not secure without HTTPS. Token-Based Authentication: Utilizes tokens (e.g., JWT) for secure access.
- 13. CONCLUSION • Application Layer Protocols:Crucial for facilitating communication between diverse applications over the internet. • HTTP and HTTPS:HTTP is essential for data transfer, while HTTPS provides a secure channel through encryption. • Web Services:REST and SOAP frameworks offer different advantages for building APIs based on specific needs. • HTTP Status Codes:Critical for understanding the outcomes of requests and troubleshooting issues
- 15. THANK YOU