Added by Soren Stoutner over 6 years ago. Updated over 2 years ago.
0%
Description
https://redmine.stoutner.com/issues/246 removed it on the loading of all base (main frame) URLs, but not for resource requests.
As part of this, there needs to be a domain setting that can specify the referer heading. Otherwise, some websites will not load.
It looks like this can be done using `shouldInterceptRequest()`.
It might also be possible to remove other undesirable headers at the same time, but further testing will be required to be sure and to assess the impact on the loading of requests.
It is unclear to me how many websites would actually have problems if the referer header were removed from resource requests. I will have to do some testing, but I might decide to remove the functionality without any ability to override it, as websites needs to get used to working without expecting a referer header.