DotNetBrowser.Net Namespace

The upload data as bytes. Can be empty if the form doesn't contain any data.

File data.

The list of key-value pairs each representing a segment of a form data. Can be empty if the form doesn't contain any data.

A host/port pair of the URI.

Represents the single HTTP header with all its values.

The MIME type.

The list of key-value pairs each representing a segment of a multi-part form data. Can be empty if the form doesn't contain any data.

A key-value pair that represents a segment of a multi-part form data. Can contain values corresponding a form field content, an upload file content, etc.

The scheme component of a URL.

The upload data of the text/plain content type.

Represents the URL request received from the Chromium engine.

The URL request job for the intercepted URL request, which allows you to provide the response data for this URL request.

File data.

The HTTP authorization preferences.

Represents the single HTTP header with all its values.

Allows access and modifying to the network-level activities.

The upload data associated with a `UrlRequest`. The upload data can be in the `text/plain`, `application/x-www-form-urlencoded`, or `multipart/form-data` format.The upload data type depends on the content of the `Content-Type` header. If the `Content-Type` header is missing or doesn't include a valid substring indicating the corresponding upload data type, the upload data will be in a binary format.

The upload data associated with a `UrlRequest`. The upload data can be in the `text/plain`, `application/x-www-form-urlencoded`, or `multipart/form-data` format.The upload data type depends on the content of the `Content-Type` header. If the `Content-Type` header is missing or doesn't include a valid substring indicating the corresponding upload data type, the upload data will be in a binary format.

The network errors.

The status of a URL request.

The supported SSL connection versions.