diff options
| author | Florian Bruhin <me@the-compiler.org> | 2020-11-23 19:42:20 +0100 |
|---|---|---|
| committer | Florian Bruhin <me@the-compiler.org> | 2020-11-23 20:18:12 +0100 |
| commit | 7f3d558be910475d4d6937bd030a61409b7756d8 (patch) | |
| tree | 4c5da0b77a970650cee77e48ed4f44d8b6421e95 | |
| parent | 8add70a490cbe8d3fc1e75293fca9f63d3a08fef (diff) | |
| download | qutebrowser-7f3d558be910475d4d6937bd030a61409b7756d8.tar.gz qutebrowser-7f3d558be910475d4d6937bd030a61409b7756d8.zip | |
Update changelog
| -rw-r--r-- | doc/changelog.asciidoc | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/changelog.asciidoc b/doc/changelog.asciidoc index c08d4184c..dee244a14 100644 --- a/doc/changelog.asciidoc +++ b/doc/changelog.asciidoc @@ -143,6 +143,14 @@ Fixed - As a workaround for an overzealous Microsoft Defender false-positive detecting a "trojan" in the (unprocessed) adblock list, `:adblock-update` now doesn't cache the HTTP response anymore. +- Setting the `content.headers.referer` setting to `same-domain` (the default) + was supposed to truncate referers to only the host with QtWebEngine. + Unfortunately, this functionality broke in Qt 5.14. It is now fixed again. +- With QtWebEngine 5.15, setting the `content.headers.referer` setting to + `never` did still send referers. This is now fixed. +- With the QtWebKit backend and `content.headers` set to `same-domain` (the + default), origins with the same domain but different schemes or ports were + treated as the same domain. They now are correctly treated as different domains. - (TODO) Fix for various functionality breaking in private windows with v1.14.0, after the last private window is closed. This includes: * Ad blocking |