An HTTP-Request<\/a> is a fundamental component of the Client-Server-Model<\/a>. When a user interacts with a Web-Browser<\/a>, it generates a request to a Web-Server<\/a> to fetch resources such as HTML<\/a> documents, images, or API<\/a> data. This communication is governed by the Hypertext-Transfer-Protocol<\/a>.<\/p> A request is composed of several distinct parts. The first is the request line, which includes the HTTP-Method<\/a> (such as GET, POST, or PUT) and the Request-URI<\/a>. Following this are the HTTP-Headers<\/a>, which contain metadata such as the User-Agent<\/a>, Content-Type<\/a>, and Accept-Language<\/a>. Finally, for specific methods like POST or PATCH, there is a Message-Body<\/a> containing the actual data to be transmitted to the server.<\/p> Different methods signify different intentions for the server to process. For example, a GET<\/a> request is designed to be idempotent and should only retrieve data, whereas a POST<\/a> request usually results in a state change or side effect on the server. Detailed specifications regarding these behaviors can be found on the MDN Web Docs<\/a> and the official W3C RFC 2616<\/a> documentation.<\/p> In response to these requests, servers return an HTTP-Response<\/a> which includes a Status-Code<\/a>, such as 200 (OK), 404 (Not Found), or 500 (Internal Server Error), indicating the outcome of the request attempt.<\/p>Anatomy of a Request<\/h2>
Primary Request Methods<\/h3>
Status Codes and Responses<\/h2>