{
    "content": "<h1><a href=\"..\/HTTP-Method\/\">HTTP-Method<\/a><\/h1><p>The <a href=\"..\/HTTP-Method\/\">HTTP-Method<\/a> (also known as an HTTP verb) indicates the desired action to be performed for a given <a href=\"..\/Resource\/\">Resource<\/a>. Each method implements specific semantics to ensure that <a href=\"..\/Client\/\">Client<\/a> and <a href=\"..\/Server\/\">Server<\/a> communication follows a predictable pattern. These methods are defined by the <a href=\"..\/IETF\/\">IETF<\/a> in various <a href=\"..\/RFC\/\">RFC<\/a> documents, most notably <a href=\"https:\/\/datatracker.ietf.org\/doc\/html\/rfc7231#section-4\">RFC 7231<\/a>.<\/p><h2>Primary HTTP Methods<\/h2><ul><li><strong><a href=\"..\/GET\/\">GET<\/a><\/strong>: Used to retrieve data from a server at the specified <a href=\"..\/URL\/\">URL<\/a>. It is considered a <a href=\"..\/Safe-Method\/\">Safe-Method<\/a> because it does not modify the state of the resource.<\/li><li><strong><a href=\"..\/POST\/\">POST<\/a><\/strong>: Used to send data to the server to create a new resource or trigger a specific processing action. Unlike GET, POST requests often result in a change in state.<\/li><li><strong><a href=\"..\/PUT\/\">PUT<\/a><\/strong>: Replaces the current representation of the target resource with the uploaded content. It is <a href=\"..\/Idempotent\/\">Idempotent<\/a>, meaning multiple identical requests should have the same effect as a single request.<\/li><li><strong><a href=\"..\/DELETE\/\">DELETE<\/a><\/strong>: Removes the specified resource from the server.<\/li><li><strong><a href=\"..\/PATCH\/\">PATCH<\/a><\/strong>: Applies partial modifications to a resource, offering a more efficient alternative to PUT when only small changes are needed.<\/li><li><strong><a href=\"..\/HEAD\/\">HEAD<\/a><\/strong>: Identical to GET but only transfers the status line and header section, omitting the response body.<\/li><li><strong><a href=\"..\/OPTIONS\/\">OPTIONS<\/a><\/strong>: Describes the communication options for the target resource, often used in <a href=\"..\/CORS\/\">CORS<\/a> preflight requests.<\/li><\/ul><p>Understanding the properties of these methods, such as whether they are <a href=\"..\/Cacheable\/\">Cacheable<\/a> or <a href=\"..\/Idempotent\/\">Idempotent<\/a>, is essential for <a href=\"..\/API-Design\/\">API-Design<\/a> and <a href=\"..\/REST\/\">REST<\/a> architecture. For more technical details, developers often refer to the <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Methods\">MDN Web Docs<\/a>.<\/p><h3>Related Topics<\/h3><ul><li><a href=\"..\/REST-API\/\">REST-API<\/a><\/li><li><a href=\"..\/HTTP-Status-Codes\/\">HTTP-Status-Codes<\/a><\/li><li><a href=\"..\/Web-Server\/\">Web-Server<\/a><\/li><li><a href=\"..\/Networking-Protocols\/\">Networking-Protocols<\/a><\/li><\/ul>",
    "tags": [
        "http",
        "networking",
        "web",
        "rest",
        "api",
        "protocol",
        "get",
        "post",
        "server",
        "client",
        "development",
        "internet"
    ]
}