[mirror_edk2.git] / NetworkPkg / HttpDxe / HttpImpl.h

/** @file\r
  The header files of implementation of EFI_HTTP_PROTOCOL protocol interfaces.\r
\r
  Copyright (c) 2015, Intel Corporation. All rights reserved.<BR>\r
\r
  This program and the accompanying materials\r
  are licensed and made available under the terms and conditions of the BSD License\r
  which accompanies this distribution.  The full text of the license may be found at\r
  http://opensource.org/licenses/bsd-license.php.\r
\r
  THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,\r
  WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.\r
\r
**/\r
\r
#ifndef __EFI_HTTP_IMPL_H__\r
#define __EFI_HTTP_IMPL_H__\r
\r
#define HTTP_DEFAULT_PORT        80\r
#define HTTP_END_OF_HDR_STR      "\r\n\r\n"\r
#define HTTP_CRLF_STR            "\r\n"\r
#define HTTP_VERSION_STR         "HTTP/1.1"\r
#define HTTP_VERSION_CRLF_STR    " HTTP/1.1\r\n"\r
#define HTTP_GET_STR             "GET "\r
#define HTTP_HEAD_STR            "HEAD "\r
//\r
// Connect method has maximum length according to EFI_HTTP_METHOD defined in\r
// UEFI2.5 spec so use this.\r
//\r
#define HTTP_MAXIMUM_METHOD_LEN  sizeof ("CONNECT")\r
\r
/**\r
  Returns the operational parameters for the current HTTP child instance.\r
\r
  The GetModeData() function is used to read the current mode data (operational\r
  parameters) for this HTTP protocol instance.\r
\r
  @param[in]  This                Pointer to EFI_HTTP_PROTOCOL instance.\r
  @param[out] HttpConfigData      Point to buffer for operational parameters of this\r
                                  HTTP instance.\r
\r
  @retval EFI_SUCCESS             Operation succeeded.\r
  @retval EFI_INVALID_PARAMETER   One or more of the following conditions is TRUE:\r
                                  This is NULL.\r
                                  HttpConfigData is NULL.\r
                                  HttpConfigData->AccessPoint is NULL.\r
  @retval EFI_NOT_STARTED         The HTTP instance is not configured.\r
\r
**/\r
EFI_STATUS\r
EFIAPI\r
EfiHttpGetModeData (\r
  IN  EFI_HTTP_PROTOCOL         *This,\r
  OUT EFI_HTTP_CONFIG_DATA      *HttpConfigData\r
  );\r
\r
/**\r
  Initialize or brutally reset the operational parameters for this EFI HTTP instance.\r
\r
  The Configure() function does the following:\r
  When HttpConfigData is not NULL Initialize this EFI HTTP instance by configuring\r
  timeout, local address, port, etc.\r
  When HttpConfigData is NULL, reset this EFI HTTP instance by closing all active\r
  connections with remote hosts, canceling all asynchronous tokens, and flush request\r
  and response buffers without informing the appropriate hosts.\r
\r
  Except for GetModeData() and Configure(), No other EFI HTTP function can be executed\r
  by this instance until the Configure() function is executed and returns successfully.\r
\r
  @param[in]  This                Pointer to EFI_HTTP_PROTOCOL instance.\r
  @param[in]  HttpConfigData      Pointer to the configure data to configure the instance.\r
\r
  @retval EFI_SUCCESS             Operation succeeded.\r
  @retval EFI_INVALID_PARAMETER   One or more of the following conditions is TRUE:\r
                                  This is NULL.\r
                                  HttpConfigData->LocalAddressIsIPv6 is FALSE and\r
                                  HttpConfigData->IPv4Node is NULL.\r
                                  HttpConfigData->LocalAddressIsIPv6 is TRUE and\r
                                  HttpConfigData->IPv6Node is NULL.\r
  @retval EFI_ALREADY_STARTED     Reinitialize this HTTP instance without calling\r
                                  Configure() with NULL to reset it.\r
  @retval EFI_DEVICE_ERROR        An unexpected system or network error occurred.\r
  @retval EFI_OUT_OF_RESOURCES    Could not allocate enough system resources when\r
                                  executing Configure().\r
  @retval EFI_UNSUPPORTED         One or more options in ConfigData are not supported\r
                                  in the implementation.\r
**/\r
EFI_STATUS\r
EFIAPI\r
EfiHttpConfigure (\r
  IN  EFI_HTTP_PROTOCOL         *This,\r
  IN  EFI_HTTP_CONFIG_DATA      *HttpConfigData\r
  );\r
\r
/**\r
  The Request() function queues an HTTP request to this HTTP instance.\r
\r
  Similar to Transmit() function in the EFI TCP driver. When the HTTP request is sent\r
  successfully, or if there is an error, Status in token will be updated and Event will\r
  be signaled.\r
\r
  @param[in]  This                Pointer to EFI_HTTP_PROTOCOL instance.\r
  @param[in]  Token               Pointer to storage containing HTTP request token.\r
\r
  @retval EFI_SUCCESS             Outgoing data was processed.\r
  @retval EFI_NOT_STARTED         This EFI HTTP Protocol instance has not been started.\r
  @retval EFI_DEVICE_ERROR        An unexpected system or network error occurred.\r
  @retval EFI_TIMEOUT             Data was dropped out of the transmit or receive queue.\r
  @retval EFI_OUT_OF_RESOURCES    Could not allocate enough system resources.\r
  @retval EFI_UNSUPPORTED         The HTTP method is not supported in current\r
                                  implementation.\r
  @retval EFI_INVALID_PARAMETER   One or more of the following conditions is TRUE:\r
                                  This is NULL.\r
                                  Token->Message is NULL.\r
                                  Token->Message->Body is not NULL,\r
                                  Token->Message->BodyLength is non-zero, and\r
                                  Token->Message->Data is NULL, but a previous call to\r
                                  Request()has not been completed successfully.\r
**/\r
EFI_STATUS\r
EFIAPI\r
EfiHttpRequest (\r
  IN  EFI_HTTP_PROTOCOL         *This,\r
  IN  EFI_HTTP_TOKEN            *Token\r
  );\r
\r
/**\r
  Abort an asynchronous HTTP request or response token.\r
\r
  The Cancel() function aborts a pending HTTP request or response transaction. If\r
  Token is not NULL and the token is in transmit or receive queues when it is being\r
  cancelled, its Token->Status will be set to EFI_ABORTED and then Token->Event will\r
  be signaled. If the token is not in one of the queues, which usually means that the\r
  asynchronous operation has completed, EFI_NOT_FOUND is returned. If Token is NULL,\r
  all asynchronous tokens issued by Request() or Response() will be aborted.\r
\r
  @param[in]  This                Pointer to EFI_HTTP_PROTOCOL instance.\r
  @param[in]  Token               Point to storage containing HTTP request or response\r
                                  token.\r
\r
  @retval EFI_SUCCESS             Request and Response queues are successfully flushed.\r
  @retval EFI_INVALID_PARAMETER   This is NULL.\r
  @retval EFI_NOT_STARTED         This instance hasn't been configured.\r
  @retval EFI_NO_MAPPING          When using the default address, configuration (DHCP,\r
                                  BOOTP, RARP, etc.) hasn't finished yet.\r
  @retval EFI_NOT_FOUND           The asynchronous request or response token is not\r
                                  found.\r
  @retval EFI_UNSUPPORTED         The implementation does not support this function.\r
**/\r
EFI_STATUS\r
EFIAPI\r
EfiHttpCancel (\r
  IN  EFI_HTTP_PROTOCOL         *This,\r
  IN  EFI_HTTP_TOKEN            *Token\r
  );\r
\r
/**\r
  The Response() function queues an HTTP response to this HTTP instance, similar to\r
  Receive() function in the EFI TCP driver. When the HTTP request is sent successfully,\r
  or if there is an error, Status in token will be updated and Event will be signaled.\r
\r
  The HTTP driver will queue a receive token to the underlying TCP instance. When data\r
  is received in the underlying TCP instance, the data will be parsed and Token will\r
  be populated with the response data. If the data received from the remote host\r
  contains an incomplete or invalid HTTP header, the HTTP driver will continue waiting\r
  (asynchronously) for more data to be sent from the remote host before signaling\r
  Event in Token.\r
\r
  It is the responsibility of the caller to allocate a buffer for Body and specify the\r
  size in BodyLength. If the remote host provides a response that contains a content\r
  body, up to BodyLength bytes will be copied from the receive buffer into Body and\r
  BodyLength will be updated with the amount of bytes received and copied to Body. This\r
  allows the client to download a large file in chunks instead of into one contiguous\r
  block of memory. Similar to HTTP request, if Body is not NULL and BodyLength is\r
  non-zero and all other fields are NULL or 0, the HTTP driver will queue a receive\r
  token to underlying TCP instance. If data arrives in the receive buffer, up to\r
  BodyLength bytes of data will be copied to Body. The HTTP driver will then update\r
  BodyLength with the amount of bytes received and copied to Body.\r
\r
  If the HTTP driver does not have an open underlying TCP connection with the host\r
  specified in the response URL, Request() will return EFI_ACCESS_DENIED. This is\r
  consistent with RFC 2616 recommendation that HTTP clients should attempt to maintain\r
  an open TCP connection between client and host.\r
\r
  @param[in]  This                Pointer to EFI_HTTP_PROTOCOL instance.\r
  @param[in]  Token               Pointer to storage containing HTTP response token.\r
\r
  @retval EFI_SUCCESS             Allocation succeeded.\r
  @retval EFI_NOT_STARTED         This EFI HTTP Protocol instance has not been\r
                                  initialized.\r
  @retval EFI_INVALID_PARAMETER   One or more of the following conditions is TRUE:\r
                                  This is NULL.\r
                                  Token is NULL.\r
                                  Token->Message->Headers is NULL.\r
                                  Token->Message is NULL.\r
                                  Token->Message->Body is not NULL,\r
                                  Token->Message->BodyLength is non-zero, and\r
                                  Token->Message->Data is NULL, but a previous call to\r
                                  Response() has not been completed successfully.\r
  @retval EFI_OUT_OF_RESOURCES    Could not allocate enough system resources.\r
  @retval EFI_ACCESS_DENIED       An open TCP connection is not present with the host\r
                                  specified by response URL.\r
**/\r
EFI_STATUS\r
EFIAPI\r
EfiHttpResponse (\r
  IN  EFI_HTTP_PROTOCOL         *This,\r
  IN  EFI_HTTP_TOKEN            *Token\r
  );\r
\r
/**\r
  The Poll() function can be used by network drivers and applications to increase the\r
  rate that data packets are moved between the communication devices and the transmit\r
  and receive queues.\r
\r
  In some systems, the periodic timer event in the managed network driver may not poll\r
  the underlying communications device fast enough to transmit and/or receive all data\r
  packets without missing incoming packets or dropping outgoing packets. Drivers and\r
  applications that are experiencing packet loss should try calling the Poll() function\r
  more often.\r
\r
  @param[in]  This                Pointer to EFI_HTTP_PROTOCOL instance.\r
\r
  @retval EFI_SUCCESS             Incoming or outgoing data was processed.\r
  @retval EFI_DEVICE_ERROR        An unexpected system or network error occurred.\r
  @retval EFI_INVALID_PARAMETER   This is NULL.\r
  @retval EFI_NOT_READY           No incoming or outgoing data is processed.\r
  @retval EFI_NOT_STARTED         This EFI HTTP Protocol instance has not been started.\r
\r
**/\r
EFI_STATUS\r
EFIAPI\r
EfiHttpPoll (\r
  IN  EFI_HTTP_PROTOCOL         *This\r
  );\r
\r
extern EFI_HTTP_PROTOCOL  mEfiHttpTemplate;\r
\r
#endif\r
Commit	Line	Data
47f51a06 YT	1	/** @file\r
	2	The header files of implementation of EFI_HTTP_PROTOCOL protocol interfaces.\r
	3	\r
	4	Copyright (c) 2015, Intel Corporation. All rights reserved.<BR>\r
	5	\r
	6	This program and the accompanying materials\r
	7	are licensed and made available under the terms and conditions of the BSD License\r
	8	which accompanies this distribution. The full text of the license may be found at\r
	9	http://opensource.org/licenses/bsd-license.php.\r
	10	\r
	11	THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,\r
	12	WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.\r
	13	\r
	14	**/\r
	15	\r
	16	#ifndef __EFI_HTTP_IMPL_H__\r
	17	#define __EFI_HTTP_IMPL_H__\r
	18	\r
	19	#define HTTP_DEFAULT_PORT 80\r
	20	#define HTTP_END_OF_HDR_STR "\r\n\r\n"\r
	21	#define HTTP_CRLF_STR "\r\n"\r
	22	#define HTTP_VERSION_STR "HTTP/1.1"\r
	23	#define HTTP_VERSION_CRLF_STR " HTTP/1.1\r\n"\r
	24	#define HTTP_GET_STR "GET "\r
	25	#define HTTP_HEAD_STR "HEAD "\r
	26	//\r
	27	// Connect method has maximum length according to EFI_HTTP_METHOD defined in\r
	28	// UEFI2.5 spec so use this.\r
	29	//\r
	30	#define HTTP_MAXIMUM_METHOD_LEN sizeof ("CONNECT")\r
	31	\r
	32	/**\r
	33	Returns the operational parameters for the current HTTP child instance.\r
	34	\r
	35	The GetModeData() function is used to read the current mode data (operational\r
	36	parameters) for this HTTP protocol instance.\r
	37	\r
	38	@param[in] This Pointer to EFI_HTTP_PROTOCOL instance.\r
	39	@param[out] HttpConfigData Point to buffer for operational parameters of this\r
	40	HTTP instance.\r
	41	\r
	42	@retval EFI_SUCCESS Operation succeeded.\r
	43	@retval EFI_INVALID_PARAMETER One or more of the following conditions is TRUE:\r
	44	This is NULL.\r
	45	HttpConfigData is NULL.\r
	46	HttpConfigData->AccessPoint is NULL.\r
	47	@retval EFI_NOT_STARTED The HTTP instance is not configured.\r
	48	\r
	49	**/\r
	50	EFI_STATUS\r
	51	EFIAPI\r
	52	EfiHttpGetModeData (\r
	53	IN EFI_HTTP_PROTOCOL *This,\r
	54	OUT EFI_HTTP_CONFIG_DATA *HttpConfigData\r
	55	);\r
	56	\r
	57	/**\r
	58	Initialize or brutally reset the operational parameters for this EFI HTTP instance.\r
	59	\r
	60	The Configure() function does the following:\r
	61	When HttpConfigData is not NULL Initialize this EFI HTTP instance by configuring\r
	62	timeout, local address, port, etc.\r
	63	When HttpConfigData is NULL, reset this EFI HTTP instance by closing all active\r
	64	connections with remote hosts, canceling all asynchronous tokens, and flush request\r
65	and response buffers without informing the appropriate hosts.\r
66	\r
67	Except for GetModeData() and Configure(), No other EFI HTTP function can be executed\r
68	by this instance until the Configure() function is executed and returns successfully.\r
69	\r
70	@param[in] This Pointer to EFI_HTTP_PROTOCOL instance.\r
71	@param[in] HttpConfigData Pointer to the configure data to configure the instance.\r
72	\r
73	@retval EFI_SUCCESS Operation succeeded.\r
74	@retval EFI_INVALID_PARAMETER One or more of the following conditions is TRUE:\r
75	This is NULL.\r
76	HttpConfigData->LocalAddressIsIPv6 is FALSE and\r
77	HttpConfigData->IPv4Node is NULL.\r
78	HttpConfigData->LocalAddressIsIPv6 is TRUE and\r
79	HttpConfigData->IPv6Node is NULL.\r
80	@retval EFI_ALREADY_STARTED Reinitialize this HTTP instance without calling\r
81	Configure() with NULL to reset it.\r
82	@retval EFI_DEVICE_ERROR An unexpected system or network error occurred.\r
83	@retval EFI_OUT_OF_RESOURCES Could not allocate enough system resources when\r
84	executing Configure().\r
85	@retval EFI_UNSUPPORTED One or more options in ConfigData are not supported\r
86	in the implementation.\r
87	**/\r
88	EFI_STATUS\r
89	EFIAPI\r
90	EfiHttpConfigure (\r
91	IN EFI_HTTP_PROTOCOL *This,\r
92	IN EFI_HTTP_CONFIG_DATA *HttpConfigData\r
93	);\r
94	\r
95	/**\r
96	The Request() function queues an HTTP request to this HTTP instance.\r
97	\r
98	Similar to Transmit() function in the EFI TCP driver. When the HTTP request is sent\r
99	successfully, or if there is an error, Status in token will be updated and Event will\r
100	be signaled.\r
101	\r
102	@param[in] This Pointer to EFI_HTTP_PROTOCOL instance.\r
103	@param[in] Token Pointer to storage containing HTTP request token.\r
104	\r
105	@retval EFI_SUCCESS Outgoing data was processed.\r
106	@retval EFI_NOT_STARTED This EFI HTTP Protocol instance has not been started.\r
107	@retval EFI_DEVICE_ERROR An unexpected system or network error occurred.\r
108	@retval EFI_TIMEOUT Data was dropped out of the transmit or receive queue.\r
109	@retval EFI_OUT_OF_RESOURCES Could not allocate enough system resources.\r
110	@retval EFI_UNSUPPORTED The HTTP method is not supported in current\r
111	implementation.\r
112	@retval EFI_INVALID_PARAMETER One or more of the following conditions is TRUE:\r
113	This is NULL.\r
114	Token->Message is NULL.\r
115	Token->Message->Body is not NULL,\r
116	Token->Message->BodyLength is non-zero, and\r
117	Token->Message->Data is NULL, but a previous call to\r
118	Request()has not been completed successfully.\r
119	**/\r
120	EFI_STATUS\r
121	EFIAPI\r
122	EfiHttpRequest (\r
123	IN EFI_HTTP_PROTOCOL *This,\r
124	IN EFI_HTTP_TOKEN *Token\r
125	);\r
126	\r
127	/**\r
128	Abort an asynchronous HTTP request or response token.\r
129	\r
130	The Cancel() function aborts a pending HTTP request or response transaction. If\r
131	Token is not NULL and the token is in transmit or receive queues when it is being\r
132	cancelled, its Token->Status will be set to EFI_ABORTED and then Token->Event will\r
133	be signaled. If the token is not in one of the queues, which usually means that the\r
134	asynchronous operation has completed, EFI_NOT_FOUND is returned. If Token is NULL,\r
135	all asynchronous tokens issued by Request() or Response() will be aborted.\r
136	\r
137	@param[in] This Pointer to EFI_HTTP_PROTOCOL instance.\r
138	@param[in] Token Point to storage containing HTTP request or response\r
139	token.\r
140	\r
141	@retval EFI_SUCCESS Request and Response queues are successfully flushed.\r
142	@retval EFI_INVALID_PARAMETER This is NULL.\r
143	@retval EFI_NOT_STARTED This instance hasn't been configured.\r
144	@retval EFI_NO_MAPPING When using the default address, configuration (DHCP,\r
145	BOOTP, RARP, etc.) hasn't finished yet.\r
146	@retval EFI_NOT_FOUND The asynchronous request or response token is not\r
147	found.\r
148	@retval EFI_UNSUPPORTED The implementation does not support this function.\r
149	**/\r
150	EFI_STATUS\r
151	EFIAPI\r
152	EfiHttpCancel (\r
153	IN EFI_HTTP_PROTOCOL *This,\r
154	IN EFI_HTTP_TOKEN *Token\r
155	);\r
156	\r
157	/**\r
158	The Response() function queues an HTTP response to this HTTP instance, similar to\r
159	Receive() function in the EFI TCP driver. When the HTTP request is sent successfully,\r
160	or if there is an error, Status in token will be updated and Event will be signaled.\r
161	\r
162	The HTTP driver will queue a receive token to the underlying TCP instance. When data\r
163	is received in the underlying TCP instance, the data will be parsed and Token will\r
164	be populated with the response data. If the data received from the remote host\r
165	contains an incomplete or invalid HTTP header, the HTTP driver will continue waiting\r
166	(asynchronously) for more data to be sent from the remote host before signaling\r
167	Event in Token.\r
168	\r
169	It is the responsibility of the caller to allocate a buffer for Body and specify the\r
170	size in BodyLength. If the remote host provides a response that contains a content\r
171	body, up to BodyLength bytes will be copied from the receive buffer into Body and\r
172	BodyLength will be updated with the amount of bytes received and copied to Body. This\r
173	allows the client to download a large file in chunks instead of into one contiguous\r
174	block of memory. Similar to HTTP request, if Body is not NULL and BodyLength is\r
175	non-zero and all other fields are NULL or 0, the HTTP driver will queue a receive\r
176	token to underlying TCP instance. If data arrives in the receive buffer, up to\r
177	BodyLength bytes of data will be copied to Body. The HTTP driver will then update\r
178	BodyLength with the amount of bytes received and copied to Body.\r
179	\r
180	If the HTTP driver does not have an open underlying TCP connection with the host\r
181	specified in the response URL, Request() will return EFI_ACCESS_DENIED. This is\r
182	consistent with RFC 2616 recommendation that HTTP clients should attempt to maintain\r
183	an open TCP connection between client and host.\r
184	\r
185	@param[in] This Pointer to EFI_HTTP_PROTOCOL instance.\r
186	@param[in] Token Pointer to storage containing HTTP response token.\r
187	\r
188	@retval EFI_SUCCESS Allocation succeeded.\r
189	@retval EFI_NOT_STARTED This EFI HTTP Protocol instance has not been\r
190	initialized.\r
191	@retval EFI_INVALID_PARAMETER One or more of the following conditions is TRUE:\r
192	This is NULL.\r
193	Token is NULL.\r
194	Token->Message->Headers is NULL.\r
195	Token->Message is NULL.\r
196	Token->Message->Body is not NULL,\r
197	Token->Message->BodyLength is non-zero, and\r
198	Token->Message->Data is NULL, but a previous call to\r
199	Response() has not been completed successfully.\r
200	@retval EFI_OUT_OF_RESOURCES Could not allocate enough system resources.\r
201	@retval EFI_ACCESS_DENIED An open TCP connection is not present with the host\r
202	specified by response URL.\r
203	**/\r
204	EFI_STATUS\r
205	EFIAPI\r
206	EfiHttpResponse (\r
207	IN EFI_HTTP_PROTOCOL *This,\r
208	IN EFI_HTTP_TOKEN *Token\r
209	);\r
210	\r
211	/**\r
212	The Poll() function can be used by network drivers and applications to increase the\r
213	rate that data packets are moved between the communication devices and the transmit\r
214	and receive queues.\r
215	\r
216	In some systems, the periodic timer event in the managed network driver may not poll\r
217	the underlying communications device fast enough to transmit and/or receive all data\r
218	packets without missing incoming packets or dropping outgoing packets. Drivers and\r
219	applications that are experiencing packet loss should try calling the Poll() function\r
220	more often.\r
221	\r
222	@param[in] This Pointer to EFI_HTTP_PROTOCOL instance.\r
223	\r
224	@retval EFI_SUCCESS Incoming or outgoing data was processed.\r
225	@retval EFI_DEVICE_ERROR An unexpected system or network error occurred.\r
226	@retval EFI_INVALID_PARAMETER This is NULL.\r
227	@retval EFI_NOT_READY No incoming or outgoing data is processed.\r
228	@retval EFI_NOT_STARTED This EFI HTTP Protocol instance has not been started.\r
229	\r
230	**/\r
231	EFI_STATUS\r
232	EFIAPI\r
233	EfiHttpPoll (\r
234	IN EFI_HTTP_PROTOCOL *This\r
235	);\r
236	\r
237	extern EFI_HTTP_PROTOCOL mEfiHttpTemplate;\r
238	\r
239	#endif\r