Lines Matching full:http

2   This file defines the EFI HTTP Protocol interface. It is split into
4 HTTP Service Binding Protocol (HTTPSB)
5 HTTP Protocol (HTTP)
110 /// Set to TRUE to instruct the EFI HTTP instance to use the default address
152 /// HTTP version that this instance will support.
185 /// The HTTP method (e.g. GET, POST) for this HTTP Request.
189 /// The URI of a remote host. From the information in this field, the HTTP instance
190 /// will be able to determine whether to use HTTP or HTTPS and will also be able to
191 /// determine the port number to use. If no port number is specified, port 80 (HTTP)
228 /// HTTP message data.
232 /// When the token is used to send a HTTP request, Request is a pointer to storage that
233 /// contains such data as URL and HTTP method.
237 /// When used to await a response, Response points to storage containing HTTP response
243 /// Number of HTTP header structures in Headers list. On request, this count is
244 /// provided by the caller. On response, this count is provided by the HTTP driver.
248 /// Array containing list of HTTP headers. On request, this array is populated by the
249 /// caller. On response, this array is allocated and populated by the HTTP driver. It
255 /// Length in bytes of the HTTP body. This can be zero depending on the HttpMethod type.
259 /// Body associated with the HTTP request or response. This can be NULL depending on
270 /// This Event will be signaled after the Status field is updated by the EFI HTTP
276 /// Status will be set to one of the following value if the HTTP request is
278 /// EFI_SUCCESS: The HTTP request was successfully sent to the remote host.
280 /// HTTP error. The response status code is returned in token.
281 /// EFI_ABORTED: The HTTP request was cancelled by the caller and removed from
283 /// EFI_TIMEOUT: The HTTP request timed out before reaching the remote host.
288 /// Pointer to storage containing HTTP message data.
294 Returns the operational parameters for the current HTTP child instance.
297 parameters) for this HTTP protocol instance.
301 HTTP instance. It is the responsibility of the caller
312 @retval EFI_NOT_STARTED This EFI HTTP Protocol instance has not been started.
322 Initialize or brutally reset the operational parameters for this EFI HTTP instance.
325 When HttpConfigData is not NULL Initialize this EFI HTTP instance by configuring
327 When HttpConfigData is NULL, reset this EFI HTTP instance by closing all active
331 No other EFI HTTP function can be executed by this instance until the Configure()
344 @retval EFI_ALREADY_STARTED Reinitialize this HTTP instance without calling
360 The Request() function queues an HTTP request to this HTTP instance,
361 similar to Transmit() function in the EFI TCP driver. When the HTTP request is sent
366 @param[in] Token Pointer to storage containing HTTP request token.
369 @retval EFI_NOT_STARTED This EFI HTTP Protocol instance has not been started.
381 @retval EFI_UNSUPPORTED The HTTP method is not supported in current implementation.
391 Abort an asynchronous HTTP request or response token.
393 The Cancel() function aborts a pending HTTP request or response transaction. If
401 @param[in] Token Point to storage containing HTTP request or response
419 The Response() function queues an HTTP response to this HTTP instance, similar to
420 Receive() function in the EFI TCP driver. When the HTTP Response is received successfully,
423 The HTTP driver will queue a receive token to the underlying TCP instance. When data
426 contains an incomplete or invalid HTTP header, the HTTP driver will continue waiting
435 block of memory. Similar to HTTP request, if Body is not NULL and BodyLength is
436 non-zero and all other fields are NULL or 0, the HTTP driver will queue a receive
438 BodyLength bytes of data will be copied to Body. The HTTP driver will then update
441 If the HTTP driver does not have an open underlying TCP connection with the host
443 consistent with RFC 2616 recommendation that HTTP clients should attempt to maintain
447 @param[in] Token Pointer to storage containing HTTP response token.
450 @retval EFI_NOT_STARTED This EFI HTTP Protocol instance has not been
489 @retval EFI_NOT_STARTED This EFI HTTP Protocol instance has not been started.
498 /// The EFI HTTP protocol is designed to be used by EFI drivers and applications to
499 /// create and transmit HTTP Requests, as well as handle HTTP responses that are