From 58765f2b8d263ad780cd8d9eeab83a7e3f6116c5 Mon Sep 17 00:00:00 2001 From: Florian Bruhin Date: Fri, 10 Jul 2020 12:53:54 +0200 Subject: Clarify how per-domain settings work for content.cookies.accept (cherry picked from commit 6c9b088834d10fd6861551bf8ede5f896706a1ac) --- doc/help/settings.asciidoc | 1 + qutebrowser/config/configdata.yml | 3 +++ 2 files changed, 4 insertions(+) diff --git a/doc/help/settings.asciidoc b/doc/help/settings.asciidoc index 9f784dc03..6ee816837 100644 --- a/doc/help/settings.asciidoc +++ b/doc/help/settings.asciidoc @@ -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. diff --git a/qutebrowser/config/configdata.yml b/qutebrowser/config/configdata.yml index 2fc70d520..58229838a 100644 --- a/qutebrowser/config/configdata.yml +++ b/qutebrowser/config/configdata.yml @@ -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 -- cgit v1.2.3-54-g00ecf