BrowserLaunchContext <TOptions, Launcher>
Hierarchy
- BrowserPluginOptions<TOptions>
- BrowserLaunchContext
Index
Properties
optionalbrowserPerProxy
optionalexperimentalContainersexperimental
Like useIncognitoPages
, but for persistent contexts, so cache is used for faster loading.
Works best with Firefox. Unstable on Chromium.
optionallaunchOptions
Options that will be passed down to the automation library. E.g.
puppeteer.launch(launchOptions);
. This is a good place to set
options that you want to apply as defaults. To dynamically override
those options per-browser, see the preLaunchHooks
of BrowserPool.
optionallauncher
The type of browser to be launched.
By default, chromium
is used. Other browsers like webkit
or firefox
can be used.
optionalproxyUrl
URL to an HTTP proxy server. It must define the port number, and it may also contain proxy username and password.
optionaluseChrome
If true
and the executablePath
option of launchOptions
is not set,
the launcher will launch full Google Chrome browser available on the machine
rather than the bundled Chromium. The path to Chrome executable
is taken from the CRAWLEE_CHROME_EXECUTABLE_PATH
environment variable if provided,
or defaults to the typical Google Chrome executable location specific for the operating system.
optionaluseIncognitoPages
With this option selected, all pages will be opened in a new incognito browser context. This means they will not share cookies nor cache and their resources will not be throttled by one another.
optionaluserAgent
The User-Agent
HTTP header used by the browser.
If not provided, the function sets User-Agent
to a reasonable default
to reduce the chance of detection of the crawler.
optionaluserDataDir
Sets the User Data Directory path. The user data directory contains profile data such as history, bookmarks, and cookies, as well as other per-installation local state. If not specified, a temporary directory is used instead.
If set to
true
, the crawler respects the proxy url generated for the given request. This aligns the browser-based crawlers with theHttpCrawler
.Might cause performance issues, as Crawlee might launch too many browser instances.