Abstract:

This video tutorial demonstrates how to build a basic web server and website from scratch using only the C++ standard library. It covers fundamental concepts of socket programming, handling platform-specific differences for Windows and other operating systems, and implementing logic for both GET and POST HTTP requests. The tutorial progresses through initializing the socket, binding it to a host and port, listening for incoming connections, parsing client requests, rendering static HTML files, and extracting data from POST requests to generate dynamic responses. Key aspects include header file management, error handling, and the structured approach to building a functional, albeit simple, C++ web application.

Building a Web Server from Scratch in C++

• 0:00 Introduction & Setup: The video begins by outlining the goal: creating a C++ web server and website using only standard libraries. It then proceeds to include essential header files like iostream, fstream, sstream, string, map, vector, and cstring.
• 0:48 Platform-Specific Socket Libraries: The tutorial highlights critical differences between Windows and other operating systems for socket programming.
  • On Windows, Winsock2.h is required, along with linking WS2_32.lib.
  • For other systems, sys/socket.h and netinet/in.h are used.
• 2:25 Server Initialization (run_server function): The core run_server function is introduced, setting up the host (127.0.0.1 for localhost) and port (8080).
  • 3:16 WinSock Initialization (Windows Only): On Windows, WSAStartup is called to initialize the WinSock library, with error checking.
  • 4:31 Socket Creation: A server socket is created using socket() (AF_INET for IPv4, SOCK_STREAM for TCP), with error handling for invalid sockets.
  • 5:59 Server Address Configuration & Binding: A sockaddr_in structure is populated with the server's family (AF_INET), IP address (using inet_addr), and port (converted to network byte order using htons). The socket is then bind() to this address, again with error checks.
  • 8:43 Listening for Connections: The server is put into a listening state using listen(), configured to accept a maximum of one pending connection in its queue.
• 11:04 HTML Rendering Setup:
  • A std::map named URL_mappings is created to associate URL paths (e.g., "/") with their corresponding HTML template file paths (e.g., "templates/index.html").
  • Example HTML files (index.html, about.html) are created in a "templates" folder.
• 12:15 Handling Requests (handle_request function): This function is responsible for sending HTTP responses to clients.
  • It checks if the requested path exists in URL_mappings.
  • If found, it reads the content of the associated HTML file.
  • It constructs an HTTP response string including headers (e.g., "HTTP/1.1 200 OK", "Content-Type: text/html") and the HTML content.
  • If the path is not found, a "404 Not Found" response with an error message is generated.
  • The response is sent to the client socket, and the client socket is closed.
• 17:33 Parsing Requests (parse_request function): This helper function extracts the HTTP method (GET, POST) and the requested path from the incoming client request string.
  • It uses std::istringstream to process the request line by line and tokenizes the first line to identify the method and path.
  • It returns a std::pair<std::string, std::string> containing the method and path.
• 21:29 Main Server Loop & Error Handling: The run_server function enters an infinite while(true) loop within a try-catch block to continuously handle incoming connections and exceptions.
  • 23:22 Accepting Client Connections: Inside the loop, accept() is called to block until an incoming connection arrives, creating a new client socket for communication.
  • 26:45 Receiving Client Data: recv() is used to read the incoming HTTP request data from the client socket into a buffer. Error handling is included for receive failures or closed connections.
  • 28:38 Integrating parse_request: The received request data is passed to parse_request to get the HTTP method and path.
  • 30:11 Testing GET Requests: After compilation and execution, the server successfully serves index.html and about.html, and displays "404 Not Found" for non-existent paths.
• 30:48 Handling POST Requests:
  • 30:48 HTML Form Setup: HTML forms are added to index.html and about.html with method="post" and an input field named "name" to submit data.
  • 32:11 handle_post_request function: This new function processes POST data.
    • It takes the client socket, content length, and POST data as arguments.
    • It parses the POST data (e.g., "name=YourName") into key-value pairs (std::map).
    • It then generates a dynamic HTTP response, including a greeting like "Hello YourName" along with the original HTML content.
  • 39:39 Differentiating GET and POST: The main handle_request function is modified to check the method (obtained from parse_request) and content_length to determine if it's a GET or POST request. It then calls handle_post_request accordingly.
  • 42:17 Extracting Content Length and POST Data: In run_server, when a POST request is detected, logic is added to extract the Content-Length header and the actual POST data from the request body.
• 46:25 Final Testing: The server is recompiled and run. Testing with the forms confirms that POST requests are handled correctly, and the server displays personalized greetings based on the submitted name.
• 46:50 Conclusion: The video concludes, confirming the successful creation of a basic C++ web server that handles both GET and POST requests.