MdePkg/Http: Add EFI_HTTP_CONNECT_REQUEST_DATA structure

Introduce EFI_HTTP_CONNECT_REQUEST_DATA structure to handle HTTP
CONNECT requests

Implementation based on UEFI Specification v2.11 Section 29.6.6
Added EFI_HTTP_CONNECT_REQUEST_DATA structure for HttpMethodConnect
usage in EFI_HTTP_PROTOCOL.Request()

Signed-off-by: Saloni Kasbekar <saloni.kasbear@intel.com>

1 files changed, 16 insertions, 1 deletions

diff --git a/MdePkg/Include/Protocol/Http.h b/MdePkg/Include/Protocol/Http.h
index 7d9481a..79e5357 100644
--- a/MdePkg/Include/Protocol/Http.h
+++ b/MdePkg/Include/Protocol/Http.h
@@ -189,12 +189,27 @@ typedef struct {
   /// The URI of a remote host. From the information in this field, the HTTP instance

   /// will be able to determine whether to use HTTP or HTTPS and will also be able to

   /// determine the port number to use. If no port number is specified, port 80 (HTTP)

-  /// is assumed. See RFC 3986 for more details on URI syntax.

+  /// or 443 (HTTPS) is assumed. See RFC 3986 for more details on URI syntax.

   ///

   CHAR16             *Url;

 } EFI_HTTP_REQUEST_DATA;

 

 ///

+/// EFI_HTTP_CONNECT_REQUEST_DATA

+///

+typedef struct {

+  EFI_HTTP_REQUEST_DATA    Base;

+  ///

+  /// The URI of an Proxy Host. This field will be NULL if there is no Proxy Host

+  /// in the device path. From the information in this field, the HTTP instance will

+  /// be able to determine whether to use HTTP or HTTPS and will also be able to

+  /// determine the port number to use. If no port number is specified, port 80 (HTTP)

+  /// or 443 (HTTPS) is assumed. See RFC 3986 for more details on URI syntax.

+  ///

+  CHAR16                   *ProxyUrl;

+} EFI_HTTP_CONNECT_REQUEST_DATA;

+

+///

 /// EFI_HTTP_RESPONSE_DATA

 ///

 typedef struct {