Skip to content

Kianibound/http-basics

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
README.md
README.md
 
 

Repository files navigation

The goal of this repo is explaining basics of HTTP with some interview questions

What is HTTP?

HTTP ((Hypertext Transfer Protocol) is a protocol used for communication between web browsers and web servers. It defines how requests from clients (such as browsers) are made and how servers respond to those requests. Let's break it down:

  • HTTP Basics: HTTP is a request-response protocol, which means a client sends a request to a server, and the server responds with a corresponding response.

  • URL: URLs (Uniform Resource Locators) are used to identify resources on the web. They typically consist of a scheme (e.g., "http://" or "https://"), followed by the domain name or IP address of the server, and the path to the resource.

Example: http://www.example.com/index.html

  • HTTP Verbs (Methods): HTTP requests are made using different verbs or methods, which indicate the action the client wants to perform. The common HTTP methods are:

    • GET: Retrieves a resource from the server.

    • POST: Sends data to the server to create a new resource.

    • PUT: Sends data to the server to update or replace an existing resource.

    • DELETE: Deletes a specified resource on the server.

  • HTTP Request Structure: An HTTP request consists of a request line, headers, and an optional body. Let's look at an example of a GET request:

GET /index.html HTTP/1.1
Host: www.example.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36

  • The first line contains the HTTP method (GET), the path of the resource (/index.html), and the HTTP version (HTTP/1.1).

  • The headers provide additional information about the request, such as the host and user agent.

  • HTTP Response Structure: An HTTP response consists of a status line, headers, and an optional body. Here's an example of an HTTP response:

HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 1274

<!DOCTYPE html>
<html>
<head>
<title>Example Page</title>
</head>
<body>
<h1>Welcome to Example Page</h1>
</body>
</html>

  • The first line contains the HTTP version, followed by the status code and reason phrase (200 OK indicates a successful response).

  • The headers provide additional information about the response, such as the content type and length.

  • The body contains the actual content of the response, such as HTML in this example.

  • Status Codes: HTTP status codes indicate the outcome of a request. Here are a few examples:

    • 200 OK: The request was successful.
    • 404 Not Found: The requested resource was not found.
    • 500 Internal Server Error: An error occurred on the server.

Commonly asked HTTP interview questions:

  • Q: What is HTTP?

    • Answer: HTTP (Hypertext Transfer Protocol) is a protocol that allows communication between web browsers and web servers. It defines how requests and responses are made and handled.

  • Q: What is the difference between HTTP and HTTPS?

    • A: HTTP is the unsecured version, while HTTPS (HTTP Secure) is the secured version of the protocol. HTTPS encrypts the data exchanged between the browser and server using SSL/TLS, providing a secure connection.

  • Q: What are HTTP methods?

    • Answer: HTTP methods are verbs used to specify the action the client wants to perform. Common methods include GET, POST, PUT, and DELETE.

  • Q: Explain the difference between GET andPOST methods.

    • Answer: The GET method is used to retrieve data from a server, while the POST method is used to send data to the server to create or update a resource. GET requests include parameters in the URL, while POST requests send data in the request body.

  • Q: What is a query parameter in an HTTP request?

    • Answer: A query parameter is additional information sent with the URL in a GET request to specify parameters for the server. It follows the URL and is indicated by a "?" followed by key-value pairs separated by "&". Example: http://www.example.com/search?query=example&page=1

  • Q: What is an HTTP status code? Give an example.

    • Answer: An HTTP status code is a three-digit number that indicates the outcome of a request. For example, status code 200 represents a successful request, while 404 indicates that the requested resource was not found.

  • Q: How do you handle an HTTP request in JavaScript using Node.js?

    • Answer: In Node.js, you can handle HTTP requests using the built-in 'http' module. Here's an example of handling a GET request:
const http = require('http');

const server = http.createServer((req, res) => {
 res.writeHead(200, { 'Content-Type': 'text/plain' });
 res.end('Hello, World!');
});

server.listen(3000);

  • Q: What is the purpose of the 'Content-Type' header?

    • Answer: The 'Content-Type' header specifies the type of data being sent in the request or response. For example, 'text/html' indicates HTML content, 'application/json' indicates JSON data, and 'image/jpeg' indicates a JPEG image.

  • Q: How does caching work in HTTP?

    • Answer: Caching allows the browser to store a copy of a resource, such as a webpage or image, to avoid making repetitive requests to the server. The 'Cache-Control' header is used to control caching behavior.

  • Q: What is Cross-Origin Resource Sharing (CORS)?

    • Answer: CORS is a mechanism that allows restricted resources on a web page to be requested from another domain outside the domain from which the resource originated. It involves adding appropriate headers to the response to control which domains are allowed to access the resource.

  • Q: What is the purpose of the 'User-Agent' header in an HTTP request?

    • Answer The 'User-Agent' header provides information about the client (usually a web browser) that is making the request. It helps servers to understand the capabilities and characteristics of the client.

  • Q: What is the 'Content-Length' header used for?

    • Answer The 'Content-Length' header specifies the size of the request or response body in bytes. It allows the server or client to determine the length of the data being sent or received.

  • Q: Explain the difference between HTTP 1.0 and HTTP 1.1.

    • Answer: HTTP 1.1 introduced persistent connections, allowing multiple requests and responses to be sent over a single connection, reducing overhead. It also added support for chunked transfer encoding and introduced various improvements in caching, security, and performance.

  • Q: What is the purpose of URL encoding in HTTP?

    • Answer: URL encoding is used to convert special characters or reserved characters in a URL to a format that can be safely transmitted. It ensures that the URL remains valid and doesn't cause any conflicts or parsing issues.

  • Q: What is an HTTP cookie?

    • Answer: An HTTP cookie is a small piece of data stored by a web browser. Cookies are sent with every subsequent request to the same domain, allowing servers to maintain stateful sessions and remember user-specific information.

  • Q: What is the purpose of the 'Referer' header in an HTTP request?

    • Answer: The 'Referer' (yes, it's spelled that way) header indicates the URL of the previous web page from which the current request originated. It can be useful for tracking and analytics purposes.

  • Q: What is the role of the 'Host' header in an HTTP request?

    • Answer: The 'Host' header specifies the domain name of the server being addressed in the request. It enables hosting multiple websites on the same IP address and helps the server route the request to the appropriate website.

  • Q: Explain the purpose of the 'ETag' header in HTTP responses.

    • Answer: The 'ETag' header provides an identifier (usually a hash) for a specific version of a resource. It helps in efficient caching and enables conditional requests, allowing the server to respond with a 304 Not Modified status if the resource hasn't changed.

  • Q: What is a redirect in HTTP?

    • Answer: A redirect is a response sent by the server that instructs the client to request a different URL. This can be useful for handling moved resources, implementing URL aliases, or redirecting users to a different page.

  • Q: What are the differences between HTTP and WebSocket?

    • Answer: HTTP is a request-response protocol, while WebSocket is a bidirectional communication protocol that provides full-duplex communication channels over a single TCP connection. WebSocket enables real-time communication between clients and servers, whereas HTTP requires separate requests for each interaction.

More about ETags :

In HTTP, an ETag (Entity Tag) is an identifier assigned to a specific version of a resource on the server. It helps in efficient caching and enables conditional requests, allowing the server to respond with a 304 Not Modified status if the resource hasn't changed since the previous request. Here's an example to illustrate its usage:

  1. Imagine you have a website that displays a user's profile information. The profile data is retrieved from a server via an HTTP request.

  2. When the user initially visits their profile page, the server responds with the user's profile data and includes an ETag header. Let's say the ETag value is "abc123" for this version of the user's profile.

  3. The user continues browsing the website and makes subsequent requests to view their profile. The browser includes the ETag value received earlier in the request's headers.

  4. On receiving the subsequent request, the server compares the provided ETag value with the current ETag value of the user's profile. If they match, it means the profile hasn't changed since the last request.

  5. In the case where the ETag values match, the server can respond with a 304 Not Modified status instead of sending the entire profile data again. This saves bandwidth and improves performance.

  6. If the ETag values don't match, it means the profile has been modified on the server. In this case, the server generates a new version of the profile data, assigns a new ETag value (e.g., "def456"), and includes it in the response. The server then sends the updated profile data to the browser.

  7. By leveraging ETags, the browser can efficiently determine whether it needs to retrieve a resource from the server or if it can use a cached version. This reduces unnecessary network traffic and optimizes the user experience.

To summarize, ETags act as fingerprints or unique identifiers for resources. They enable conditional requests, allowing servers to respond with a minimal response when the resource hasn't changed, thereby reducing bandwidth usage and improving performance.

Keep in mind that ETags can be implemented differently depending on the server and framework being used. Some servers generate ETags based on file timestamps or content hashes, while others may use a different approach.

Code Example:

const http = require('http');
const crypto = require('crypto');

// Simulated user profile data
let userProfile = {
  id: 1,
  name: 'John Doe',
  email: 'john@example.com',
};

// Generate the initial ETag for the user profile
const initialETag = generateETag(userProfile);

// Helper function to generate an ETag
function generateETag(data) {
  const hash = crypto.createHash('md5').update(JSON.stringify(data)).digest('hex');
  return `"${hash}"`;
}

// Create an HTTP server
const server = http.createServer((req, res) => {
  if (req.url === '/profile') {
    // Set the ETag header to the initial ETag value
    res.setHeader('ETag', initialETag);

    if (req.headers['if-none-match'] === initialETag) {
      // If the provided ETag matches the current ETag, send a 304 Not Modified status
      res.statusCode = 304;
      res.end();
    } else {
      // If the ETags don't match, send the updated user profile
      res.setHeader('Content-Type', 'application/json');
      
      // Set Cache-Control header to enable caching for 1 hour (3600 seconds)
      res.setHeader('Cache-Control', 'public, max-age=3600');
      
      res.statusCode = 200;
      res.end(JSON.stringify(userProfile));
    }
  } else {
    // Handle other routes or resources
    res.statusCode = 404;
    res.end();
  }
});

// Start the server
server.listen(3000, () => {
  console.log('Server is running on port 3000');
});

In this example, we have added the Cache-Control header to enable caching of the user profile resource. The Cache-Control header provides instructions to the client and intermediaries on how to handle caching for the response.

By setting the Cache-Control header to public, max-age=3600, we specify that the response can be cached by the client and other intermediaries for a maximum of 1 hour (3600 seconds).

When a client makes a request to /profile, the server includes the Cache-Control header in the response, allowing the client to cache the response for subsequent requests within the specified timeframe.

If a subsequent request is made within the caching timeframe and the provided ETag matches the current ETag, the server responds with a 304 Not Modified status, indicating that the client can use its cached version of the user profile.

This enables efficient caching of the user profile resource, reducing the need for the server to send the complete response if the profile hasn't changed and allowing the client to utilize its cached version.

Common HTTP status codes:

  • 1xx Informational Codes:

    • 100 Continue: The server has received the initial part of the request, and the client should proceed with sending the remaining part.

  • 2xx Success Codes:

    • 200 OK: The request was successful, and the server has returned the requested resource.
    • 201 Created: The request was successful, and a new resource was created as a result.
    • 204 No Content: The server successfully processed the request, but no content is returned in the response.

  • 3xx Redirection Codes:

    • 301 Moved Permanently: The requested resource has been permanently moved to a new URL.
    • 302 Found: The requested resource has been temporarily moved to a different URL.
    • 304 Not Modified: The requested resource has not been modified since the last request, and the client can use its cached version.

  • 4xx Client Error Codes:

    • 400 Bad Request: The server cannot process the request due to a client error.
    • 401 Unauthorized: The request requires authentication. The client must provide valid credentials.
    • 403 Forbidden: The server understands the request, but the client does not have sufficient permissions to access the resource.
    • 404 Not Found: The server could not find the requested resource.

  • 5xx Server Error Codes:

    • 500 Internal Server Error: An unexpected error occurred on the server.
    • 502 Bad Gateway: The server acting as a gateway received an invalid response from an upstream server.
    • 503 Service Unavailable: The server is temporarily unable to handle the request due to maintenance or high load.
    • 504 Gateway Timeout: The server acting as a gateway did not receive a timely response from an upstream server.

It's important to note that there are many more HTTP status codes available, each serving a specific purpose. These are just the most commonly encountered ones.

About

No description, website, or topics provided.

Resources

Readme
Activity

Stars

0 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

 
 
 

Contributors