WebEngineProfile QML Type
Contains settings, scripts, and visited links common to multiple web engine views. More...
| Import Statement: | import QtWebEngine 1.3 |
| Since: | QtWebEngine 1.1 |
| Instantiates: | QQuickWebEngineProfile |
Properties
- cachePath : string
- httpAcceptLanguage : string
- httpCacheMaximumSize : int
- httpCacheType : enumeration
- httpUserAgent : string
- offTheRecord : bool
- persistentCookiesPolicy : enumeration
- persistentStoragePath : string
- storageName : string
Signals
- downloadFinished(WebEngineDownloadItem download)
- downloadRequested(WebEngineDownloadItem download)
Methods
- void clearHttpCache()
Detailed Description
WebEngineProfile contains settings, scripts, and the list of visited links shared by all views that belong to the profile. As such, profiles can be used to isolate views from each other. A typical use case is a dedicated profile for a 'private browsing' mode.
Each web engine view has an associated profile. Views that do not have a specific profile set share a common default one.
Property Documentation
The path to the location where the profile's caches are stored, in particular the HTTP cache.
By default, the caches are stored below QStandardPaths::writableLocation(QStandardPaths::CacheLocation) in a directory named using storageName.
The value of the Accept-Language HTTP request-header field.
This QML property was introduced in QtWebEngine 1.2.
The maximum size of the HTTP cache. If 0, the size will be controlled automatically by QtWebEngine. The default value is 0.
See also httpCacheType.
This enumeration describes the type of the HTTP cache:
| Constant | Description |
|---|---|
WebEngineProfile.MemoryHttpCache | Uses an in-memory cache. This is the only setting possible if offTheRecord is set or no persistentStoragePath is available. |
WebEngineProfile.DiskHttpCache | Uses a disk cache. This is the default value. |
WebEngineProfile.NoCache | Disables caching. (Added in 5.7) |
Whether the web engine profile is off-the-record. An off-the-record profile forces cookies, the HTTP cache, and other normally persistent data to be stored only in memory.
This enumeration describes the policy of cookie persistency:
| Constant | Description |
|---|---|
WebEngineProfile.NoPersistentCookies | Both session and persistent cookies are stored in memory. This is the only setting possible if offTheRecord is set or no persistentStoragePath is available. |
WebEngineProfile.AllowPersistentCookies | Cookies marked persistent are saved to and restored from disk, whereas session cookies are only stored to disk for crash recovery. This is the default setting. |
WebEngineProfile.ForcePersistentCookies | Both session and persistent cookies are saved to and restored from disk. |
The path to the location where the persistent data for the browser and web content are stored. Persistent data includes persistent cookies, HTML5 local storage, and visited links.
By default, the storage is located below QStandardPaths::writableLocation(QStandardPaths::DataLocation) in a directory named using storageName.
The storage name that is used to create separate subdirectories for each profile that uses the disk for storing persistent data and cache.
See also WebEngineProfile::persistentStoragePath and WebEngineProfile::cachePath.
Signal Documentation
downloadFinished(WebEngineDownloadItem download) |
This signal is emitted whenever downloading stops, because it finished successfully, was cancelled, or was interrupted (for example, because connectivity was lost). The download argument holds the state of the finished download instance.
downloadRequested(WebEngineDownloadItem download) |
This signal is emitted whenever a download has been triggered. The download argument holds the state of the download. The download has to be explicitly accepted with WebEngineDownloadItem::accept() or the download will be cancelled by default.
Method Documentation
Removes the profile's cache entries.
This QML method was introduced in QtWebEngine 1.3.
See also WebEngineProfile::cachePath.