Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cefsharp.github.io/api/118.6.x/html/T_CefSharp_IRequestContext.htm below:

A request context provides request handling for a set of related browser or URL request objects. A request context can be specified when creating a new browser by setting the

property (Passing in via the constructor for the OffScreen control is preferred). Browser objects with different request contexts will never be hosted in the same render process. Browser objects with the same request context may or may not be hosted in the same render process depending on the process model.Browser objects created indirectly via the JavaScript window.open function or targeted links will share the same render process and the same request context as the source browser.

CefSharp (in CefSharp.dll) Version: 118.6.80.0 (118.6.80.0)

public interface IRequestContext : IDisposable

public interface class IRequestContext : IDisposable

The IRequestContext type exposes the following members.

Returns the cache path for this object. If empty an "incognito mode" in-memory cache is being used.

Gets a value indicating whether the RequestContext has been disposed of.

Returns true if this object is the global context. The global context is used by default when creating a browser or URL request with a NULL context argument.

Returns true if the preference with the specified name can be modified using SetPreference. As one example preferences set via the command-line usually cannot be modified. This method must be called on the CEF UI thread.

Clears all certificate exceptions that were added as part of handling

. If you call this it is recommended that you also call

or you risk not being prompted again for server certificates if you reconnect quickly.

Clears all HTTP authentication credentials that were added as part of handling

.

Clear all registered scheme handler factories.

Clears all active and idle connections that Chromium currently has. This is only recommended if you have released all other CEF objects but don't yet want to call Cef.Shutdown().

Returns true if this context was used to load the extension identified by extensionId. Other contexts sharing the same storage will also have access to the extension (see HasExtension). This method must be called on the CEF UI thread.

Performs application-defined tasks associated with freeing, releasing, or resetting unmanaged resources.

Returns all preferences as a dictionary. The returned object contains a copy of the underlying preference values and modifications to the returned object will not modify the underlying preference values. This method must be called on the browser process UI thread.

Returns the default cookie manager for this object. This will be the global cookie manager if this object is the global request context.

Returns the extension matching extensionId or null if no matching extension is accessible in this context (see HasExtension). This method must be called on the CEF UI thread.

Retrieve the list of all extensions that this context has access to (see HasExtension). extensionIds will be populated with the list of extension ID values. This method must be called on the CEF UI thread.

Returns the value for the preference with the specified name. Returns NULL if the preference does not exist. The returned object contains a copy of the underlying preference value and modifications to the returned object will not modify the underlying preference value. This method must be called on the CEF UI thread.

Returns true if this context has access to the extension identified by extensionId. This may not be the context that was used to load the extension (see DidLoadExtension). This method must be called on the CEF UI thread.

Returns true if a preference with the specified name exists. This method must be called on the CEF UI thread.

Returns true if this object is pointing to the same context object.

Returns true if this object is sharing the same storage as the specified context.

Load an extension. If extension resources will be read from disk using the default load implementation then rootDirectoy should be the absolute path to the extension resources directory and manifestJson should be null. If extension resources will be provided by the client (e.g. via IRequestHandler and/or IExtensionHandler) then rootDirectory should be a path component unique to the extension (if not absolute this will be internally prefixed with the PK_DIR_RESOURCES path) and manifestJson should contain the contents that would otherwise be read from the "manifest.json" file on disk. The loaded extension will be accessible in all contexts sharing the same storage (HasExtension returns true). However, only the context on which this method was called is considered the loader (DidLoadExtension returns true) and only the loader will receive IRequestContextHandler callbacks for the extension.

will be called on load success or

will be called on load failure. If the extension specifies a background script via the "background" manifest key then

will be called to create the background browser. See that method for additional information about background scripts. For visible extension views the client application should evaluate the manifest to determine the correct extension URL to load and then load the extension URL in a ChromiumWebBrowser instance after the extension has loaded. For example, the client can look for the "browser_action" manifest key as documented at https://developer.chrome.com/extensions/browserAction. Extension URLs take the form "chrome-extension://<extension_id>/<path>" Browsers that host extensions differ from normal browsers as follows: - Can access chrome.* JavaScript APIs if allowed by the manifest. Visit chrome://extensions-support for the list of extension APIs currently supported by CEF. - Main frame navigation to non-extension content is blocked. - Pinch-zooming is disabled. -

returns the hosted extension. - CefBrowserHost::IsBackgroundHost returns true for background hosts. See https://developer.chrome.com/extensions for extension implementation and usage documentation.

Register a scheme handler factory for the specified schemeName and optional domainName. An empty domainName value for a standard scheme will cause the factory to match all domain names. The domainName value will be ignored for non-standard schemes. If schemeName is a built-in scheme and no handler is returned by factory then the built-in scheme handler factory will be called. If schemeName is a custom scheme then you must also implement the CefApp::OnRegisterCustomSchemes() method in all processes. This function may be called multiple times to change or remove the factory that matches the specified schemeName and optional domainName.

Attempts to resolve origin to a list of associated IP addresses.

Set the value associated with preference name. If value is null the preference will be restored to its default value. If setting the preference fails then error will be populated with a detailed description of the problem. This method must be called on the CEF UI thread. Preferences set via the command-line usually cannot be modified.

Used internally to get the underlying IRequestContext instance. Unlikely you'll use this yourself.

Clears all HTTP authentication credentials that were added as part of handling

.

Gets the cookie manager associated with the IRequestContext. Once the cookie manager storage has been initialized the method will return.

Load an extension from the given directory. To load a crx file you must unzip it first. For further details see

Load extension(s) from the given directory. This methods obtains all the sub directories of

and calls

if manifest.json is found in the sub folder. To load crx file(s) you must unzip them first. For further details see

Extension method to register a instance of the

with the provided

for the

Set the value associated with preference name. If value is null the preference will be restored to its default value. If setting the preference fails then error will be populated with a detailed description of the problem. This method must be called on the CEF UI thread. Preferences set via the command-line usually cannot be modified.

Sets the proxy server for the specified IRequestContext. Protocol for the proxy server is http MUST be called on the CEF UI Thread

Sets the proxy server for the specified IRequestContext. Protocol for the proxy server is http MUST be called on the CEF UI Thread

Sets the proxy server for the specified IRequestContext MUST be called on the CEF UI Thread

Sets the proxy server for the specified IRequestContext. Protocol for the proxy server is http

Sets the proxy server for the specified IRequestContext

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4