mirror
/
qutebrowser
mirror of https://github.com/qutebrowser/qutebrowser.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify how per-domain settings work for content.cookies.accept 

(cherry picked from commit 6c9b088834)
This commit is contained in:
Florian Bruhin 2020-07-10 12:53:54 +02:00
parent 63c2d1bebb
commit 58765f2b8d
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/help/settings.asciidoc
View File

@ -1944,6 +1944,7 @@ This setting is only available with the QtWebEngine backend.
Which cookies to accept.
With QtWebEngine, this setting also controls other features with tracking capabilities similar to those of cookies; including IndexedDB, DOM storage, filesystem API, service workers, and AppCache.
Note that with QtWebKit, only `all` and `never` are supported as per-domain values. Setting `no-3rdparty` or `no-unknown-3rdparty` per-domain on QtWebKit will have the same effect as `all`.
If this setting is used with URL patterns, the pattern gets applied to the origin/first party URL of the page making the request, not the request URL.
This setting supports URL patterns.

3
qutebrowser/config/configdata.yml
View File

@ -373,6 +373,9 @@ content.cookies.accept:
values. Setting `no-3rdparty` or `no-unknown-3rdparty` per-domain on
QtWebKit will have the same effect as `all`.
If this setting is used with URL patterns, the pattern gets applied to the
origin/first party URL of the page making the request, not the request URL.
content.cookies.store:
default: true
type: Bool