Send a DELETE request.
DELETE(url = NULL, config = list(), ..., body = NULL,
encode = c("multipart", "form", "json", "raw"), handle = NULL)the url of the page to retrieve
Additional configuration settings such as http
authentication (authenticate), additional headers
(add_headers), cookies (set_cookies) etc.
See config for full details and list of helpers.
Further named parameters, such as query, path, etc,
passed on to modify_url. Unnamed parameters will be combined
with config.
One of the following:
FALSE: No body. This is typically not used with POST,
PUT, or PATCH, but can be useful if you need to send a
bodyless request (like GET) with VERB().
NULL: An empty body
"": A length 0 body
upload_file("path/"): The contents of a file. The mime
type will be guessed from the extension, or can be supplied explicitly
as the second argument to upload_file()
A character or raw vector: sent as is in body. Use
content_type to tell the server what sort of data
you are sending.
A named list: See details for encode.
If the body is a named list, how should it be encoded? Can be one of form (application/x-www-form-urlencoded), multipart, (multipart/form-data), or json (application/json).
For "multipart", list elements can be strings or objects created by
upload_file. For "form", elements are coerced to strings
and escaped, use I() to prevent double-escaping. For "json",
parameters are automatically "unboxed" (i.e. length 1 vectors are
converted to scalars). To preserve a length 1 vector as a vector,
wrap in I(). For "raw", either a character or raw vector. You'll
need to make sure to set the content_type() yourself.
The handle to use with this request. If not
supplied, will be retrieved and reused from the handle_pool
based on the scheme, hostname and port of the url. By default httr
requests to the same scheme/host/port combo. This substantially reduces
connection time, and ensures that cookies are maintained over multiple
requests to the same host. See handle_pool for more
details.
The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method MAY be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation has been carried out, even if the status code returned from the origin server indicates that the action has been completed successfully. However, the server SHOULD NOT indicate success unless, at the time the response is given, it intends to delete the resource or move it to an inaccessible location.
A successful response SHOULD be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted, or 204 (No Content) if the action has been enacted but the response does not include an entity.
If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries SHOULD be treated as stale. Responses to this method are not cacheable.
Other http methods: BROWSE,
GET, HEAD,
PATCH, POST,
PUT, VERB
# NOT RUN {
DELETE("http://httpbin.org/delete")
POST("http://httpbin.org/delete")
# }
Run the code above in your browser using DataLab