From f1d8dc59d79bf16d378885a628c96aa8a3036b74 Mon Sep 17 00:00:00 2001 From: Florian Bruhin Date: Thu, 20 Jan 2022 12:15:24 +0100 Subject: Allow empty strings for content.headers.custom --- doc/changelog.asciidoc | 2 ++ qutebrowser/config/configdata.yml | 1 + 2 files changed, 3 insertions(+) diff --git a/doc/changelog.asciidoc b/doc/changelog.asciidoc index ff32bf011..a446ec534 100644 --- a/doc/changelog.asciidoc +++ b/doc/changelog.asciidoc @@ -45,6 +45,8 @@ Changed - The `qute-bitwarden` userscript understands a new `--password-prompt-invocation`, which can be used to specify a tool other than `rofi` to ask for a password. +- The `content.headers.custom` setting now accepts empty strings as values, + resulting in an empty header being sent. Added ~~~~~ diff --git a/qutebrowser/config/configdata.yml b/qutebrowser/config/configdata.yml index b0d9c6364..cf5e4665a 100644 --- a/qutebrowser/config/configdata.yml +++ b/qutebrowser/config/configdata.yml @@ -616,6 +616,7 @@ content.headers.custom: valtype: name: String encoding: ascii + none_ok: true none_ok: true supports_pattern: true desc: Custom headers for qutebrowser HTTP requests. -- cgit v1.2.3-54-g00ecf