From c211d44c0d23c5f1633b8fe9c3237410574b686a Mon Sep 17 00:00:00 2001 From: Florian Bruhin Date: Wed, 1 Jul 2020 10:48:57 +0200 Subject: Document how content.proxy can have a delay Closes #5557 (cherry picked from commit 7a7410d9064fece78fdf73c603cc2a3011eb2c92) --- 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 8d248a5d8..9f784dc03 100644 --- a/doc/help/settings.asciidoc +++ b/doc/help/settings.asciidoc @@ -2448,6 +2448,7 @@ Default: +pass:[false]+ === content.proxy Proxy to use. In addition to the listed values, you can use a `socks://...` or `http://...` URL. +Note that with QtWebEngine, it will take a couple of seconds until the change is applied, if this value is changed at runtime. Type: <> diff --git a/qutebrowser/config/configdata.yml b/qutebrowser/config/configdata.yml index e8b7d51bb..2fc70d520 100644 --- a/qutebrowser/config/configdata.yml +++ b/qutebrowser/config/configdata.yml @@ -815,6 +815,9 @@ content.proxy: In addition to the listed values, you can use a `socks://...` or `http://...` URL. + Note that with QtWebEngine, it will take a couple of seconds until the + change is applied, if this value is changed at runtime. + content.proxy_dns_requests: default: true type: Bool -- cgit v1.2.3-54-g00ecf