Métodos de Petición

  1. GET

    Solicita una representación de un recurso especificado. Las peticiones que usen GET deberían limitarse a obtener los datos y no tener ningún otro efecto.

  2. HEAD

    Pregunta por la misma respuesta que una petición GET pero sin el cuerpo de la respuesta

  3. POST

    Requests that the server accept the entity enclosed in the request as a new subordinate of the web resource identified by the URI. The data POSTed might be, as examples,

    1. an annotation for existing resources;
    2. a message for a bulletin board, newsgroup, mailing list, or comment thread;
    3. a block of data that is the result of submitting a web form to a data-handling process;
    4. or an item to add to a database.
  4. PUT

    Requests that the enclosed entity be stored under the supplied URI. If the URI refers to an already existing resource, it is modified; if the URI does not point to an existing resource, then the server can create the resource with that URI.


    Deletes the specified resource.

  6. TRACE

    Echoes back the received request so that a client can see what (if any) changes or additions have been made by intermediate servers.


    Returns the HTTP methods that the server supports for the specified URL. This can be used to check the functionality of a web server by requesting * instead of a specific resource.


    Converts the request connection to a transparent TCP/IP tunnel, usually to facilitate SSL-encrypted communication (HTTPS) through an unencrypted HTTP proxy.

  9. PATCH

    Is used to apply partial modifications to a resource. HTTP servers are required to implement at least the GET and HEAD methods and, whenever possible, also the OPTIONS method

The HTTP methods POST and PUT aren't the HTTP equivalent of the CRUD's create and update. They both serve a different purpose. It's quite possible, valid and even preferred in some occasions, to use POST to create resources, or use PUT to update resources.

Use PUT when you can update a resource completely through a specific resource.

For instance, if you know that an article resides at http://example.org/article/1234, you can PUT a new resource representation of this article directly through a PUT on this URL.

If you do not know the actual resource location, for instance, when you add a new article, but do not have any idea where to store it, you can POST it to an URL, and let the server decide the actual URL.

Casiano Rodriguez León 2015-06-18