0144a314ad
Similarly to #5998, XHR requests should be able to set their custom Accept-Language values - and for some odd reason, stuff breaks on websites sometimes when that's not respected. There's no way for qutebrowser to know if a given header value is already set in a request (i.e. whether we're adding or overriding). Thus we only really have two options here: 1) Don't set any shared.custom_headers() for XHR requests at all. 2) Special-case Accept-Language here, because the issue usually is triggered by the global override, but that already gets set just fine via QWebEngineProfile anyways. Given that 2) is the thing causing trouble in the wild and it's unclear what the desired behavior for 1) is (e.g. for the DNT header), let's go for 2) here. |
||
|---|---|---|
| .. | ||
| hello.txt.html | ||
| jseval.html | ||
| jseval_file.js | ||
| pyeval_file.py | ||
| qutescheme_csrf.html | ||
| test.pdf | ||
| xhr_headers.html | ||