[mirror_edk2.git] / RedfishPkg / RedfishRestExDxe / RedfishRestExProtocol.c

/** @file\r
  Implementation of Redfish EFI_REST_EX_PROTOCOL interfaces.\r
\r
   Copyright (c) 2019, Intel Corporation. All rights reserved.<BR>\r
  (C) Copyright 2020 Hewlett Packard Enterprise Development LP<BR>\r
\r
  SPDX-License-Identifier: BSD-2-Clause-Patent\r
\r
**/\r
#include <Uefi.h>\r
#include "RedfishRestExInternal.h"\r
\r
EFI_REST_EX_PROTOCOL  mRedfishRestExProtocol = {\r
  RedfishRestExSendReceive,\r
  RedfishRestExGetServiceTime,\r
  RedfishRestExGetService,\r
  RedfishRestExGetModeData,\r
  RedfishRestExConfigure,\r
  RedfishRestExAyncSendReceive,\r
  RedfishRestExEventService\r
};\r
\r
/**\r
  Provides a simple HTTP-like interface to send and receive resources from a REST service.\r
\r
  The SendReceive() function sends an HTTP request to this REST service, and returns a\r
  response when the data is retrieved from the service. RequestMessage contains the HTTP\r
  request to the REST resource identified by RequestMessage.Request.Url. The\r
  ResponseMessage is the returned HTTP response for that request, including any HTTP\r
  status.\r
\r
  @param[in]  This                Pointer to EFI_REST_EX_PROTOCOL instance for a particular\r
                                  REST service.\r
  @param[in]  RequestMessage      Pointer to the HTTP request data for this resource\r
  @param[out] ResponseMessage     Pointer to the HTTP response data obtained for this requested.\r
\r
  @retval EFI_SUCCESS             operation succeeded.\r
  @retval EFI_INVALID_PARAMETER   This, RequestMessage, or ResponseMessage are NULL.\r
  @retval EFI_DEVICE_ERROR        An unexpected system or network error occurred.\r
  @retval EFI_ACCESS_DENIED       HTTP method is not allowed on this URL.\r
  @retval EFI_BAD_BUFFER_SIZE     The payload is to large to be handled on server side.\r
  @retval EFI_UNSUPPORTED         Unsupported HTTP response.\r
\r
**/\r
EFI_STATUS\r
EFIAPI\r
RedfishRestExSendReceive (\r
  IN      EFI_REST_EX_PROTOCOL   *This,\r
  IN      EFI_HTTP_MESSAGE       *RequestMessage,\r
  OUT     EFI_HTTP_MESSAGE       *ResponseMessage\r
  )\r
{\r
  EFI_STATUS             Status;\r
  RESTEX_INSTANCE        *Instance;\r
  HTTP_IO_RESPONSE_DATA  *ResponseData;\r
  UINTN                  TotalReceivedSize;\r
  UINTN                  Index;\r
  LIST_ENTRY             *ChunkListLink;\r
  HTTP_IO_CHUNKS        *ThisChunk;\r
  BOOLEAN                CopyChunkData;\r
  BOOLEAN                MediaPresent;\r
  EFI_HTTP_HEADER        *PreservedRequestHeaders;\r
  BOOLEAN                ItsWrite;\r
  BOOLEAN                IsGetChunkedTransfer;\r
  HTTP_IO_SEND_CHUNK_PROCESS     SendChunkProcess;\r
  HTTP_IO_SEND_NON_CHUNK_PROCESS SendNonChunkProcess;\r
  EFI_HTTP_MESSAGE       ChunkTransferRequestMessage;\r
\r
  Status            = EFI_SUCCESS;\r
  ResponseData      = NULL;\r
  IsGetChunkedTransfer = FALSE;\r
  SendChunkProcess = HttpIoSendChunkNone;\r
  SendNonChunkProcess = HttpIoSendNonChunkNone;\r
\r
  //\r
  // Validate the parameters\r
  //\r
  if ((This == NULL) || (RequestMessage == NULL) || ResponseMessage == NULL) {\r
    return EFI_INVALID_PARAMETER;\r
  }\r
\r
  Instance = RESTEX_INSTANCE_FROM_THIS (This);\r
\r
  //\r
  // Check Media Status.\r
  //\r
  MediaPresent = TRUE;\r
  NetLibDetectMedia (Instance->Service->ControllerHandle, &MediaPresent);\r
  if (!MediaPresent) {\r
    DEBUG ((DEBUG_INFO, "RedfishRestExSendReceive(): No MediaPresent.\n"));\r
    return EFI_NO_MEDIA;\r
  }\r
\r
  DEBUG ((DEBUG_INFO, "\nRedfishRestExSendReceive():\n"));\r
  DEBUG ((DEBUG_INFO, "*** Perform HTTP Request Method - %d, URL: %s\n", RequestMessage->Data.Request->Method, RequestMessage->Data.Request->Url));\r
\r
  //\r
  // Add header "Expect" to server, only for URL write.\r
  //\r
  Status = RedfishHttpAddExpectation (This, RequestMessage, &PreservedRequestHeaders, &ItsWrite);\r
  if (EFI_ERROR (Status)) {\r
    return Status;\r
  }\r
  if (ItsWrite == TRUE) {\r
    if (RequestMessage->BodyLength > HTTP_IO_MAX_SEND_PAYLOAD) {\r
      //\r
      // Send chunked transfer.\r
      //\r
      SendChunkProcess ++;\r
      CopyMem ((VOID *)&ChunkTransferRequestMessage, (VOID *)RequestMessage, sizeof (EFI_HTTP_MESSAGE));\r
    } else {\r
      SendNonChunkProcess ++;\r
    }\r
  }\r
ReSendRequest:;\r
  //\r
  // Send out the request to REST service.\r
  //\r
  if (ItsWrite == TRUE) {\r
    //\r
    // This is write to URI\r
    //\r
    if (SendChunkProcess > HttpIoSendChunkNone) {\r
      //\r
      // This is chunk transfer for writing large payload.\r
      // Send request header first and then handle the\r
      // following request message body using chunk transfer.\r
      //\r
      do {\r
        Status = HttpIoSendChunkedTransfer(\r
                   &(Instance->HttpIo),\r
                   &SendChunkProcess,\r
                   &ChunkTransferRequestMessage\r
                   );\r
        if (EFI_ERROR (Status)) {\r
          goto ON_EXIT;\r
        }\r
      } while (SendChunkProcess == HttpIoSendChunkContent || SendChunkProcess == HttpIoSendChunkEndChunk);\r
    } else {\r
      //\r
      // This is the non-chunk transfer, send request header first and then\r
      // handle the following request message body using chunk transfer.\r
      //\r
      Status = HttpIoSendRequest(\r
                 &(Instance->HttpIo),\r
                 (SendNonChunkProcess == HttpIoSendNonChunkContent)? NULL: RequestMessage->Data.Request,\r
                 (SendNonChunkProcess == HttpIoSendNonChunkContent)? 0: RequestMessage->HeaderCount,\r
                 (SendNonChunkProcess == HttpIoSendNonChunkContent)? NULL: RequestMessage->Headers,\r
                 (SendNonChunkProcess == HttpIoSendNonChunkHeaderZeroContent)? 0: RequestMessage->BodyLength,\r
                 (SendNonChunkProcess == HttpIoSendNonChunkHeaderZeroContent)? NULL: RequestMessage->Body\r
                 );\r
    }\r
  } else {\r
    //\r
    // This is read from URI.\r
    //\r
    Status = HttpIoSendRequest(\r
               &(Instance->HttpIo),\r
               RequestMessage->Data.Request,\r
               RequestMessage->HeaderCount,\r
               RequestMessage->Headers,\r
               RequestMessage->BodyLength,\r
               RequestMessage->Body\r
               );\r
  }\r
  if (EFI_ERROR (Status)) {\r
    goto ON_EXIT;\r
  }\r
\r
  //\r
  // ResponseMessage->Data.Response is to indicate whether to receive the HTTP header or not.\r
  // ResponseMessage->BodyLength/ResponseMessage->Body are to indicate whether to receive the response body or not.\r
  // Clean the previous buffers and all of them will be allocated later according to the actual situation.\r
  //\r
  if (ResponseMessage->Data.Response != NULL) {\r
    FreePool(ResponseMessage->Data.Response);\r
    ResponseMessage->Data.Response = NULL;\r
  }\r
\r
  ResponseMessage->BodyLength = 0;\r
  if (ResponseMessage->Body != NULL) {\r
    FreePool(ResponseMessage->Body);\r
    ResponseMessage->Body = NULL;\r
  }\r
\r
  //\r
  // Use zero BodyLength to only receive the response headers.\r
  //\r
  ResponseData = AllocateZeroPool (sizeof(HTTP_IO_RESPONSE_DATA));\r
  if (ResponseData == NULL) {\r
    Status = EFI_OUT_OF_RESOURCES;\r
    goto ON_EXIT;\r
  }\r
\r
  DEBUG ((DEBUG_INFO, "Receiving HTTP response and headers...\n"));\r
  Status = RedfishCheckHttpReceiveStatus (\r
                Instance,\r
                HttpIoRecvResponse (\r
                  &(Instance->HttpIo),\r
                  TRUE,\r
                  ResponseData\r
                  )\r
             );\r
  if (Status == EFI_NOT_READY) {\r
     goto ReSendRequest;\r
  } else if (Status == EFI_DEVICE_ERROR) {\r
    goto ON_EXIT;\r
  }\r
  //\r
  // Restore the headers if it ever changed in RedfishHttpAddExpectation().\r
  //\r
  if (RequestMessage->Headers != PreservedRequestHeaders) {\r
    FreePool (RequestMessage->Headers);\r
    RequestMessage->Headers = PreservedRequestHeaders; // Restore headers before we adding "Expect".\r
    RequestMessage->HeaderCount --;                    // Minus one header count for "Expect".\r
  }\r
\r
  DEBUG ((DEBUG_INFO, "HTTP Response StatusCode - %d:", ResponseData->Response.StatusCode));\r
  if (ResponseData->Response.StatusCode == HTTP_STATUS_200_OK) {\r
    DEBUG ((DEBUG_INFO, "HTTP_STATUS_200_OK\n"));\r
\r
    if (SendChunkProcess == HttpIoSendChunkHeaderZeroContent) {\r
      DEBUG ((DEBUG_INFO, "This is chunk transfer, start to send all chunks.", ResponseData->Response.StatusCode));\r
      SendChunkProcess ++;\r
      goto ReSendRequest;\r
    }\r
  } else if (ResponseData->Response.StatusCode == HTTP_STATUS_413_REQUEST_ENTITY_TOO_LARGE) {\r
    DEBUG ((DEBUG_INFO, "HTTP_STATUS_413_REQUEST_ENTITY_TOO_LARGE\n"));\r
\r
    Status = EFI_BAD_BUFFER_SIZE;\r
    goto ON_EXIT;\r
  } else if (ResponseData->Response.StatusCode == HTTP_STATUS_405_METHOD_NOT_ALLOWED){\r
    DEBUG ((DEBUG_ERROR, "HTTP_STATUS_405_METHOD_NOT_ALLOWED\n"));\r
\r
    Status = EFI_ACCESS_DENIED;\r
    goto ON_EXIT;\r
  } else if (ResponseData->Response.StatusCode == HTTP_STATUS_400_BAD_REQUEST) {\r
    DEBUG ((DEBUG_INFO, "HTTP_STATUS_400_BAD_REQUEST\n"));\r
    if (SendChunkProcess == HttpIoSendChunkHeaderZeroContent) {\r
      DEBUG ((DEBUG_INFO, "Bad request may caused by zero length chunk. Try to send all chunks...\n"));\r
      SendChunkProcess ++;\r
      goto ReSendRequest;\r
    }\r
  } else if (ResponseData->Response.StatusCode == HTTP_STATUS_100_CONTINUE) {\r
    DEBUG ((DEBUG_INFO, "HTTP_STATUS_100_CONTINUE\n"));\r
    if (SendChunkProcess == HttpIoSendChunkHeaderZeroContent) {\r
      //\r
      // We get HTTP_STATUS_100_CONTINUE to send the body using chunk transfer.\r
      //\r
      DEBUG ((DEBUG_INFO, "HTTP_STATUS_100_CONTINUE for chunk transfer...\n"));\r
      SendChunkProcess ++;\r
      goto ReSendRequest;\r
    }\r
    if (SendNonChunkProcess == HttpIoSendNonChunkHeaderZeroContent) {\r
      DEBUG ((DEBUG_INFO, "HTTP_STATUS_100_CONTINUE for non chunk transfer...\n"));\r
      SendNonChunkProcess ++;\r
      goto ReSendRequest;\r
    }\r
    //\r
    // It's the REST protocol's responsibility to handle the interim HTTP response (e.g. 100 Continue Informational),\r
    // and return the final response content to the caller.\r
    //\r
    if (ResponseData->Headers != NULL && ResponseData->HeaderCount != 0) {\r
      FreePool (ResponseData->Headers);\r
    }\r
    ZeroMem (ResponseData, sizeof(HTTP_IO_RESPONSE_DATA));\r
    Status = HttpIoRecvResponse (\r
               &(Instance->HttpIo),\r
               TRUE,\r
               ResponseData\r
               );\r
    if (EFI_ERROR (Status)) {\r
      goto ON_EXIT;\r
    }\r
  } else {\r
    DEBUG ((DEBUG_ERROR, "This HTTP Status is not handled!\n"));\r
    Status = EFI_UNSUPPORTED;\r
    goto ON_EXIT;\r
  }\r
\r
  //\r
  // Ready to return the StatusCode, Header info and BodyLength.\r
  //\r
  ResponseMessage->Data.Response = AllocateZeroPool (sizeof (EFI_HTTP_RESPONSE_DATA));\r
  if (ResponseMessage->Data.Response == NULL) {\r
    Status = EFI_OUT_OF_RESOURCES;\r
    goto ON_EXIT;\r
  }\r
\r
  ResponseMessage->Data.Response->StatusCode = ResponseData->Response.StatusCode;\r
  ResponseMessage->HeaderCount = ResponseData->HeaderCount;\r
  ResponseMessage->Headers = ResponseData->Headers;\r
\r
  //\r
  // Get response message body.\r
  //\r
  if (ResponseMessage->HeaderCount > 0) {\r
    Status = HttpIoGetContentLength (ResponseMessage->HeaderCount, ResponseMessage->Headers, &ResponseMessage->BodyLength);\r
    if (EFI_ERROR (Status) && Status != EFI_NOT_FOUND) {\r
      goto ON_EXIT;\r
    }\r
\r
    if (Status == EFI_NOT_FOUND) {\r
      ASSERT (ResponseMessage->BodyLength == 0);\r
    }\r
\r
    if (ResponseMessage->BodyLength == 0) {\r
      //\r
      // Check if Chunked Transfer Coding.\r
      //\r
      Status = HttpIoGetChunkedTransferContent (\r
                 &(Instance->HttpIo),\r
                 ResponseMessage->HeaderCount,\r
                 ResponseMessage->Headers,\r
                 &ChunkListLink,\r
                 &ResponseMessage->BodyLength\r
                 );\r
      if (EFI_ERROR (Status) && Status != EFI_NOT_FOUND) {\r
        goto ON_EXIT;\r
      }\r
      if (Status == EFI_SUCCESS &&\r
          ChunkListLink != NULL &&\r
          !IsListEmpty(ChunkListLink) &&\r
          ResponseMessage->BodyLength != 0) {\r
        IsGetChunkedTransfer = TRUE;\r
        //\r
        // Copy data to Message body.\r
        //\r
        CopyChunkData = TRUE;\r
        ResponseMessage->Body = AllocateZeroPool (ResponseMessage->BodyLength);\r
        if (ResponseMessage->Body == NULL) {\r
          Status = EFI_OUT_OF_RESOURCES;\r
          CopyChunkData = FALSE;\r
        }\r
        Index = 0;\r
        while (!IsListEmpty(ChunkListLink)) {\r
          ThisChunk = (HTTP_IO_CHUNKS *)GetFirstNode (ChunkListLink);\r
          if (CopyChunkData) {\r
            CopyMem(((UINT8 *)ResponseMessage->Body + Index), (UINT8 *)ThisChunk->Data, ThisChunk->Length);\r
            Index += ThisChunk->Length;\r
          }\r
          RemoveEntryList (&ThisChunk->NextChunk);\r
          FreePool ((VOID *)ThisChunk->Data);\r
          FreePool ((VOID *)ThisChunk);\r
        };\r
        FreePool ((VOID *)ChunkListLink);\r
      }\r
    }\r
    Status = EFI_SUCCESS;\r
  }\r
\r
  //\r
  // Ready to return the Body from REST service if have any.\r
  //\r
  if (ResponseMessage->BodyLength > 0 && !IsGetChunkedTransfer) {\r
    ResponseData->HeaderCount = 0;\r
    ResponseData->Headers = NULL;\r
\r
    ResponseMessage->Body = AllocateZeroPool (ResponseMessage->BodyLength);\r
    if (ResponseMessage->Body == NULL) {\r
      Status = EFI_OUT_OF_RESOURCES;\r
      goto ON_EXIT;\r
    }\r
\r
    //\r
    // Only receive the Body.\r
    //\r
    TotalReceivedSize = 0;\r
    while (TotalReceivedSize < ResponseMessage->BodyLength) {\r
      ResponseData->BodyLength = ResponseMessage->BodyLength - TotalReceivedSize;\r
      ResponseData->Body = (CHAR8 *) ResponseMessage->Body + TotalReceivedSize;\r
      Status = HttpIoRecvResponse (\r
                 &(Instance->HttpIo),\r
                 FALSE,\r
                 ResponseData\r
                 );\r
      if (EFI_ERROR (Status)) {\r
        goto ON_EXIT;\r
      }\r
\r
      TotalReceivedSize += ResponseData->BodyLength;\r
    }\r
    DEBUG ((DEBUG_INFO, "Total of lengh of Response :%d\n", TotalReceivedSize));\r
  }\r
  DEBUG ((DEBUG_INFO, "RedfishRestExSendReceive()- EFI_STATUS: %r\n", Status));\r
\r
ON_EXIT:\r
\r
  if (ResponseData != NULL) {\r
    FreePool (ResponseData);\r
  }\r
\r
  if (EFI_ERROR (Status)) {\r
    if (ResponseMessage->Data.Response != NULL) {\r
      FreePool (ResponseMessage->Data.Response);\r
      ResponseMessage->Data.Response = NULL;\r
    }\r
\r
    if (ResponseMessage->Body != NULL) {\r
      FreePool (ResponseMessage->Body);\r
      ResponseMessage->Body = NULL;\r
    }\r
  }\r
  return Status;\r
}\r
\r
/**\r
  Obtain the current time from this REST service instance.\r
\r
  The GetServiceTime() function is an optional interface to obtain the current time from\r
  this REST service instance. If this REST service does not support to retrieve the time,\r
  this function returns EFI_UNSUPPORTED. This function must returns EFI_UNSUPPORTED if\r
  EFI_REST_EX_SERVICE_TYPE returned in EFI_REST_EX_SERVICE_INFO from GetService() is\r
  EFI_REST_EX_SERVICE_UNSPECIFIC.\r
\r
  @param[in]  This                Pointer to EFI_REST_EX_PROTOCOL instance for a particular\r
                                  REST service.\r
  @param[out] Time                A pointer to storage to receive a snapshot of the current time of\r
                                  the REST service.\r
\r
  @retval EFI_SUCCESS             operation succeeded.\r
  @retval EFI_INVALID_PARAMETER   This or Time are NULL.\r
  @retval EFI_UNSUPPORTED         The RESTful service does not support returning the time.\r
  @retval EFI_DEVICE_ERROR        An unexpected system or network error occurred.\r
  @retval EFI_NOT_READY           The configuration of this instance is not set yet. Configure() must\r
                                  be executed and returns successfully prior to invoke this function.\r
\r
**/\r
EFI_STATUS\r
EFIAPI\r
RedfishRestExGetServiceTime (\r
  IN      EFI_REST_EX_PROTOCOL   *This,\r
  OUT     EFI_TIME               *Time\r
  )\r
{\r
  return EFI_UNSUPPORTED;\r
}\r
\r
/**\r
  This function returns the information of REST service provided by this EFI REST EX driver instance.\r
\r
  The information such as the type of REST service and the access mode of REST EX driver instance\r
  (In-band or Out-of-band) are described in EFI_REST_EX_SERVICE_INFO structure. For the vendor-specific\r
  REST service, vendor-specific REST service information is returned in VendorSpecifcData.\r
  REST EX driver designer is well know what REST service this REST EX driver instance intends to\r
  communicate with. The designer also well know this driver instance is used to talk to BMC through\r
  specific platform mechanism or talk to REST server through UEFI HTTP protocol. REST EX driver is\r
  responsible to fill up the correct information in EFI_REST_EX_SERVICE_INFO. EFI_REST_EX_SERVICE_INFO\r
  is referred by EFI REST clients to pickup the proper EFI REST EX driver instance to get and set resource.\r
  GetService() is a basic and mandatory function which must be able to use even Configure() is not invoked\r
  in previously.\r
\r
  @param[in]  This                Pointer to EFI_REST_EX_PROTOCOL instance for a particular\r
                                  REST service.\r
  @param[out] RestExServiceInfo   Pointer to receive a pointer to EFI_REST_EX_SERVICE_INFO structure. The\r
                                  format of EFI_REST_EX_SERVICE_INFO is version controlled for the future\r
                                  extension. The version of EFI_REST_EX_SERVICE_INFO structure is returned\r
                                  in the header within this structure. EFI REST client refers to the correct\r
                                  format of structure according to the version number. The pointer to\r
                                  EFI_REST_EX_SERVICE_INFO is a memory block allocated by EFI REST EX driver\r
                                  instance. That is caller's responsibility to free this memory when this\r
                                  structure is no longer needed. Refer to Related Definitions below for the\r
                                  definitions of EFI_REST_EX_SERVICE_INFO structure.\r
\r
  @retval EFI_SUCCESS             EFI_REST_EX_SERVICE_INFO is returned in RestExServiceInfo. This function\r
                                  is not supported in this REST EX Protocol driver instance.\r
  @retval EFI_UNSUPPORTED         This function is not supported in this REST EX Protocol driver instance.\r
\r
**/\r
EFI_STATUS\r
EFIAPI\r
RedfishRestExGetService (\r
  IN   EFI_REST_EX_PROTOCOL      *This,\r
  OUT  EFI_REST_EX_SERVICE_INFO  **RestExServiceInfo\r
  )\r
{\r
  EFI_TPL                  OldTpl;\r
  RESTEX_INSTANCE          *Instance;\r
  EFI_REST_EX_SERVICE_INFO *ServiceInfo;\r
\r
  ServiceInfo = NULL;\r
\r
  if (This == NULL || RestExServiceInfo == NULL) {\r
    return EFI_INVALID_PARAMETER;\r
  }\r
\r
  OldTpl   = gBS->RaiseTPL (TPL_CALLBACK);\r
\r
  Instance = RESTEX_INSTANCE_FROM_THIS (This);\r
\r
  ServiceInfo = AllocateZeroPool (sizeof (EFI_REST_EX_SERVICE_INFO));\r
  if (ServiceInfo == NULL) {\r
    return EFI_OUT_OF_RESOURCES;\r
  }\r
\r
  CopyMem (ServiceInfo, &(Instance->Service->RestExServiceInfo), sizeof (EFI_REST_EX_SERVICE_INFO));\r
\r
  *RestExServiceInfo = ServiceInfo;\r
\r
  gBS->RestoreTPL (OldTpl);\r
\r
  return EFI_SUCCESS;\r
}\r
\r
/**\r
  This function returns operational configuration of current EFI REST EX child instance.\r
\r
  This function returns the current configuration of EFI REST EX child instance. The format of\r
  operational configuration depends on the implementation of EFI REST EX driver instance. For\r
  example, HTTP-aware EFI REST EX driver instance uses EFI HTTP protocol as the undying protocol\r
  to communicate with REST service. In this case, the type of configuration is\r
  EFI_REST_EX_CONFIG_TYPE_HTTP returned from GetService(). EFI_HTTP_CONFIG_DATA is used as EFI REST\r
  EX configuration format and returned to EFI REST client. User has to type cast RestExConfigData\r
  to EFI_HTTP_CONFIG_DATA. For those non HTTP-aware REST EX driver instances, the type of configuration\r
  is EFI_REST_EX_CONFIG_TYPE_UNSPECIFIC returned from GetService(). In this case, the format of\r
  returning data could be non industrial. Instead, the format of configuration data is system/platform\r
  specific definition such as BMC mechanism used in EFI REST EX driver instance. EFI REST client and\r
  EFI REST EX driver instance have to refer to the specific system /platform spec which is out of UEFI scope.\r
\r
  @param[in]  This                This is the EFI_REST_EX_PROTOCOL instance.\r
  @param[out] RestExConfigData    Pointer to receive a pointer to EFI_REST_EX_CONFIG_DATA.\r
                                  The memory allocated for configuration data should be freed\r
                                  by caller. See Related Definitions for the details.\r
\r
  @retval EFI_SUCCESS             EFI_REST_EX_CONFIG_DATA is returned in successfully.\r
  @retval EFI_UNSUPPORTED         This function is not supported in this REST EX Protocol driver instance.\r
  @retval EFI_NOT_READY           The configuration of this instance is not set yet. Configure() must be\r
                                  executed and returns successfully prior to invoke this function.\r
\r
**/\r
EFI_STATUS\r
EFIAPI\r
RedfishRestExGetModeData (\r
  IN  EFI_REST_EX_PROTOCOL      *This,\r
  OUT EFI_REST_EX_CONFIG_DATA   *RestExConfigData\r
  )\r
{\r
  return EFI_UNSUPPORTED;\r
}\r
\r
/**\r
  This function is used to configure EFI REST EX child instance.\r
\r
  This function is used to configure the setting of underlying protocol of REST EX child\r
  instance. The type of configuration is according to the implementation of EFI REST EX\r
  driver instance. For example, HTTP-aware EFI REST EX driver instance uses EFI HTTP protocol\r
  as the undying protocol to communicate with REST service. The type of configuration is\r
  EFI_REST_EX_CONFIG_TYPE_HTTP and RestExConfigData is the same format with EFI_HTTP_CONFIG_DATA.\r
  Akin to HTTP configuration, REST EX child instance can be configure to use different HTTP\r
  local access point for the data transmission. Multiple REST clients may use different\r
  configuration of HTTP to distinguish themselves, such as to use the different TCP port.\r
  For those non HTTP-aware REST EX driver instance, the type of configuration is\r
  EFI_REST_EX_CONFIG_TYPE_UNSPECIFIC. RestExConfigData refers to the non industrial standard.\r
  Instead, the format of configuration data is system/platform specific definition such as BMC.\r
  In this case, EFI REST client and EFI REST EX driver instance have to refer to the specific\r
  system/platform spec which is out of the UEFI scope. Besides GetService()function, no other\r
  EFI REST EX functions can be executed by this instance until Configure()is executed and returns\r
  successfully. All other functions must returns EFI_NOT_READY if this instance is not configured\r
  yet. Set RestExConfigData to NULL means to put EFI REST EX child instance into the unconfigured\r
  state.\r
\r
  @param[in]  This                This is the EFI_REST_EX_PROTOCOL instance.\r
  @param[in]  RestExConfigData    Pointer to EFI_REST_EX_CONFIG_DATA. See Related Definitions in\r
                                  GetModeData() protocol interface.\r
\r
  @retval EFI_SUCCESS             EFI_REST_EX_CONFIG_DATA is set in successfully.\r
  @retval EFI_DEVICE_ERROR        Configuration for this REST EX child instance is failed with the given\r
                                  EFI_REST_EX_CONFIG_DATA.\r
  @retval EFI_UNSUPPORTED         This function is not supported in this REST EX Protocol driver instance.\r
\r
**/\r
EFI_STATUS\r
EFIAPI\r
RedfishRestExConfigure (\r
  IN  EFI_REST_EX_PROTOCOL    *This,\r
  IN  EFI_REST_EX_CONFIG_DATA RestExConfigData\r
  )\r
{\r
  EFI_STATUS               Status;\r
  EFI_TPL                  OldTpl;\r
  RESTEX_INSTANCE          *Instance;\r
\r
  EFI_HTTP_CONFIG_DATA     *HttpConfigData;\r
\r
  Status         = EFI_SUCCESS;\r
  HttpConfigData = NULL;\r
\r
  if (This == NULL) {\r
    return EFI_INVALID_PARAMETER;\r
  }\r
\r
  OldTpl   = gBS->RaiseTPL (TPL_CALLBACK);\r
\r
  Instance = RESTEX_INSTANCE_FROM_THIS (This);\r
\r
  if (RestExConfigData == NULL) {\r
    //\r
    // Set RestExConfigData to NULL means to put EFI REST EX child instance into the unconfigured state.\r
    //\r
    HttpIoDestroyIo (&(Instance->HttpIo));\r
\r
    if (Instance->ConfigData != NULL) {\r
      if (((EFI_REST_EX_HTTP_CONFIG_DATA *)Instance->ConfigData)->HttpConfigData.AccessPoint.IPv4Node != NULL) {\r
        FreePool(((EFI_REST_EX_HTTP_CONFIG_DATA *)Instance->ConfigData)->HttpConfigData.AccessPoint.IPv4Node);\r
      }\r
      FreePool(Instance->ConfigData);\r
      Instance->ConfigData = NULL;\r
    }\r
\r
    Instance->State = RESTEX_STATE_UNCONFIGED;\r
  } else {\r
    HttpConfigData = &((EFI_REST_EX_HTTP_CONFIG_DATA *)RestExConfigData)->HttpConfigData;\r
    Status = Instance->HttpIo.Http->Configure (Instance->HttpIo.Http, HttpConfigData);\r
    if (EFI_ERROR (Status)) {\r
      goto ON_EXIT;\r
    }\r
    Instance->HttpIo.Timeout = ((EFI_REST_EX_HTTP_CONFIG_DATA *)RestExConfigData)->SendReceiveTimeout;\r
\r
    Instance->ConfigData = AllocateZeroPool (sizeof (EFI_REST_EX_HTTP_CONFIG_DATA));\r
    if (Instance->ConfigData == NULL) {\r
      Status = EFI_OUT_OF_RESOURCES;\r
      goto ON_EXIT;\r
    }\r
    CopyMem (Instance->ConfigData, RestExConfigData, sizeof (EFI_REST_EX_HTTP_CONFIG_DATA));\r
    if (HttpConfigData->LocalAddressIsIPv6 == TRUE) {\r
      ((EFI_REST_EX_HTTP_CONFIG_DATA *)Instance->ConfigData)->HttpConfigData.AccessPoint.IPv6Node = AllocateZeroPool (sizeof (EFI_HTTPv6_ACCESS_POINT));\r
      if (((EFI_REST_EX_HTTP_CONFIG_DATA *)Instance->ConfigData)->HttpConfigData.AccessPoint.IPv6Node == NULL) {\r
        Status = EFI_OUT_OF_RESOURCES;\r
        goto ON_EXIT;\r
      }\r
      CopyMem (\r
        ((EFI_REST_EX_HTTP_CONFIG_DATA *)Instance->ConfigData)->HttpConfigData.AccessPoint.IPv6Node,\r
        HttpConfigData->AccessPoint.IPv6Node,\r
        sizeof (EFI_HTTPv6_ACCESS_POINT)\r
        );\r
    } else {\r
      ((EFI_REST_EX_HTTP_CONFIG_DATA *)Instance->ConfigData)->HttpConfigData.AccessPoint.IPv4Node = AllocateZeroPool (sizeof (EFI_HTTPv4_ACCESS_POINT));\r
      if (((EFI_REST_EX_HTTP_CONFIG_DATA *)Instance->ConfigData)->HttpConfigData.AccessPoint.IPv4Node == NULL) {\r
        Status = EFI_OUT_OF_RESOURCES;\r
        goto ON_EXIT;\r
      }\r
      CopyMem (\r
        ((EFI_REST_EX_HTTP_CONFIG_DATA *)Instance->ConfigData)->HttpConfigData.AccessPoint.IPv4Node,\r
        HttpConfigData->AccessPoint.IPv4Node,\r
        sizeof (EFI_HTTPv4_ACCESS_POINT)\r
        );\r
    }\r
    Instance->State = RESTEX_STATE_CONFIGED;\r
  }\r
\r
ON_EXIT:\r
  gBS->RestoreTPL (OldTpl);\r
  return Status;\r
}\r
\r
/**\r
  This function sends REST request to REST service and signal caller's event asynchronously when\r
  the final response is received by REST EX Protocol driver instance.\r
\r
  The essential design of this function is to handle asynchronous send/receive implicitly according\r
  to REST service asynchronous request mechanism. Caller will get the notification once the response\r
  is returned from REST service.\r
\r
  @param[in]  This                  This is the EFI_REST_EX_PROTOCOL instance.\r
  @param[in]  RequestMessage        This is the HTTP request message sent to REST service. Set RequestMessage\r
                                    to NULL to cancel the previous asynchronous request associated with the\r
                                    corresponding RestExToken. See descriptions for the details.\r
  @param[in]  RestExToken           REST EX token which REST EX Protocol instance uses to notify REST client\r
                                    the status of response of asynchronous REST request. See related definition\r
                                    of EFI_REST_EX_TOKEN.\r
  @param[in]  TimeOutInMilliSeconds The pointer to the timeout in milliseconds which REST EX Protocol driver\r
                                    instance refers as the duration to drop asynchronous REST request. NULL\r
                                    pointer means no timeout for this REST request. REST EX Protocol driver\r
                                    signals caller's event with EFI_STATUS set to EFI_TIMEOUT in RestExToken\r
                                    if REST EX Protocol can't get the response from REST service within\r
                                    TimeOutInMilliSeconds.\r
\r
  @retval EFI_SUCCESS               Asynchronous REST request is established.\r
  @retval EFI_UNSUPPORTED           This REST EX Protocol driver instance doesn't support asynchronous request.\r
  @retval EFI_TIMEOUT               Asynchronous REST request is not established and timeout is expired.\r
  @retval EFI_ABORT                 Previous asynchronous REST request has been canceled.\r
  @retval EFI_DEVICE_ERROR          Otherwise, returns EFI_DEVICE_ERROR for other errors according to HTTP Status Code.\r
  @retval EFI_NOT_READY             The configuration of this instance is not set yet. Configure() must be executed\r
                                    and returns successfully prior to invoke this function.\r
\r
**/\r
EFI_STATUS\r
EFIAPI\r
RedfishRestExAyncSendReceive (\r
  IN      EFI_REST_EX_PROTOCOL   *This,\r
  IN      EFI_HTTP_MESSAGE       *RequestMessage OPTIONAL,\r
  IN      EFI_REST_EX_TOKEN      *RestExToken,\r
  IN      UINTN                  *TimeOutInMilliSeconds OPTIONAL\r
  )\r
{\r
  return EFI_UNSUPPORTED;\r
}\r
\r
/**\r
  This function sends REST request to a REST Event service and signals caller's event\r
  token asynchronously when the URI resource change event is received by REST EX\r
  Protocol driver instance.\r
\r
  The essential design of this function is to monitor event implicitly according to\r
  REST service event service mechanism. Caller will get the notification if certain\r
  resource is changed.\r
\r
  @param[in]  This                  This is the EFI_REST_EX_PROTOCOL instance.\r
  @param[in]  RequestMessage        This is the HTTP request message sent to REST service. Set RequestMessage\r
                                    to NULL to cancel the previous event service associated with the corresponding\r
                                    RestExToken. See descriptions for the details.\r
  @param[in]  RestExToken           REST EX token which REST EX Protocol driver instance uses to notify REST client\r
                                    the URI resource which monitored by REST client has been changed. See the related\r
                                    definition of EFI_REST_EX_TOKEN in EFI_REST_EX_PROTOCOL.AsyncSendReceive().\r
\r
  @retval EFI_SUCCESS               Asynchronous REST request is established.\r
  @retval EFI_UNSUPPORTED           This REST EX Protocol driver instance doesn't support asynchronous request.\r
  @retval EFI_ABORT                 Previous asynchronous REST request has been canceled or event subscription has been\r
                                    delete from service.\r
  @retval EFI_DEVICE_ERROR          Otherwise, returns EFI_DEVICE_ERROR for other errors according to HTTP Status Code.\r
  @retval EFI_NOT_READY             The configuration of this instance is not set yet. Configure() must be executed\r
                                    and returns successfully prior to invoke this function.\r
\r
**/\r
EFI_STATUS\r
EFIAPI\r
RedfishRestExEventService (\r
  IN      EFI_REST_EX_PROTOCOL   *This,\r
  IN      EFI_HTTP_MESSAGE       *RequestMessage OPTIONAL,\r
  IN      EFI_REST_EX_TOKEN      *RestExToken\r
  )\r
{\r
  return EFI_UNSUPPORTED;\r
}\r
\r