Passer au contenu principal
  • Passer des commandes rapidement et facilement
  • Afficher les commandes et suivre l’état de votre expédition
  • Profitez de récompenses et de remises réservées aux membres
  • Créez et accédez à une liste de vos produits
  • Gérer vos sites, vos produits et vos contacts au niveau des produits Dell EMC à l’aide de la rubrique Gestion des informations de l’entreprise.

iDRAC9 with Lifecycle Controller Version 3.36.36.36 Redfish API Guide

PDF

HTTP methods

The REST API allows you to specify the type of request. It adheres to the Create, Retrieve, Update, and Delete (CRUD) standard format. The data is generated by accessing URIs that can be accessed by using the following HTTP methods:
  • GET
  • HEAD
  • POST
  • PUT
  • PATCH
  • DELETE

GET

Use the GET method to retrieve a representation of a resource. The representation can either be a single resource or a collection. Depending on the media type, the service returns the resource representation by using one of the media types specified in the Accept header. If the Accept header is not present, the service returns the resource representations either as application/json or application/xml. The resources support the formats defined by the Redfish standard.

The HTTP GET method is used to retrieve a resource. The service ignores the content of the body on a GET. The GET operation is unchanged in the absence of external changes to the resource.

HEAD

All URLs support the HEAD method. This method returns the response headers.

POST

Use the POST method to invoke actions and create a resource. The POST request is submitted to the resource collection to which the new resource belongs. Submitting a POST request to a resource that represents a collection is equivalent to submitting the request to the Members property of that resource. Services that support adding members to a collection support both forms.

Services support the POST method for creating resources. If the resource does not support this method, status code 405 is returned. The body of the create request contains a representation of the object to be created. The service can ignore any service-controlled properties such as ID, forcing those properties for the service to be overridden. The service sets the Location header to the URI of the newly created resource.

PUT

Use the PUT method to replace the property values of a resource. Properties omitted from the request body are reset to their default value. Services support the PUT method to replace a resource completely. If a service does not support this method, status code 405 is returned. Services may return a representation of the resource after any server-side transformations occur in the body of the response. The PUT operation must be unchanged in the absence of external changes to the resource. The exception is that the ETag values may change as a result of this operation.

PATCH

Use the PATCH method to update pre-existing resources. Changes to the resource are sent in the request body. This method does not change the properties that are not specified in the request body. The response is either empty or a representation of the resource after the update is done, or a success code if the operation is successful. Depending on the policies, the implementation may reject the update operation on certain fields and not apply any of the requested updates.

NOTE: Starting from iDRAC version 3.15.15.15 release, you can use the PATCH method with up to 50 attributes at a time.

DELETE

Use the DELETE method to remove a resource. Services support the DELETE method for resources that can be deleted. If the resource cannot be deleted, status code 405 is returned. Services return a representation of the deleted resource in the response body.


Évaluez ce contenu

Précis
Utile
Facile à comprendre
Avez-vous trouvé cet article utile ?
0/3000 characters
  Veuillez attribuer une note (1 à 5 étoiles).
  Veuillez attribuer une note (1 à 5 étoiles).
  Veuillez attribuer une note (1 à 5 étoiles).
  Veuillez indiquer si l’article a été utile ou non.
  Les commentaires ne doivent pas contenir les caractères spéciaux : <>()\