Click or drag to resize
CfxUrlRequest Class

[This is preliminary documentation and is subject to change.]

Structure used to make a URL request. URL requests are not associated with a browser instance so no CfxClient callbacks will be executed. URL requests can be created on any valid CEF thread in either the browser or render process. Once created the functions of the URL request object must be accessed on the same thread that created it.
Inheritance Hierarchy
SystemObject
  ChromiumCfxObject
    ChromiumCfxBase
      ChromiumCfxLibraryBase
        ChromiumCfxUrlRequest

Namespace: Chromium
Assembly: ChromiumFX (in ChromiumFX.dll)
Syntax
public class CfxUrlRequest : CfxLibraryBase

The CfxUrlRequest type exposes the following members.

Properties
  NameDescription
Public propertyClient
Returns the client.
Public propertyNativePtr
Provides access to the underlying native cef struct. This is a refcounted library struct derived from cef_base_t. Add a ref in order to keep it alive when this managed object go out of scope.
(Inherited from CfxLibraryBase.)
Public propertyRequest
Returns the request object used to create this URL request. The returned object is read-only and should not be modified.
Public propertyRequestError
Returns the request error if status is UR_CANCELED or UR_FAILED, or 0 otherwise.
Public propertyRequestStatus
Returns the request status.
Public propertyResponse
Returns the response, or NULL if no response information is available. Response information will only be available after the upload has completed. The returned object is read-only and should not be modified.
Top
Methods
  NameDescription
Public methodCancel
Cancel the request.
Public methodStatic memberCreate
Create a new URL request. Only GET, POST, HEAD, DELETE and PUT request functions are supported. Multiple post data elements are not supported and elements of type PDE_TYPE_FILE are only supported for requests originating from the browser process. Requests originating from the render process will receive the same handling as requests originating from Web content -- if the response contains Content-Disposition or Mime-Type header values that would not normally be rendered then the response may receive special handling inside the browser (for example, via the file download code path instead of the URL request code path). The |request| object will be marked as read-only after calling this function. In the browser process if |requestContext| is NULL the global request context will be used. In the render process |requestContext| must be NULL and the context associated with the current renderer process' browser will be used.
Top
Remarks
See also the original CEF documentation in cef/include/capi/cef_urlrequest_capi.h.
See Also