AdguardTeam / AdguardTeam/CoreLibs

Add `local.adguard.org` to `Connection Allowlists` response header automatically

未关闭
#2,096 0 条评论 0 个 reaction 已指派 1 人 已被 @ngorskikh 认领 在 GitHub 查看
Bug Priority: P2 Status: Code Review Version: CoreLibs v1.23
主要语言
没有语言数据
星标
52
派生
10
PR 合并指标
30 天内没有已合并 PR

描述

### Please answer the following questions for yourself before submitting an issue

- [x] Filters were updated before reproducing an issue
- [x] I checked the [knowledge base](https://adguard.com/kb/) and found no answer
- [x] I checked to make sure that this issue has not already been filed

### AdGuard version

AdGuard 8.0.0 nightly 60 (5602)

### Browser version

Chrome 151

### OS version

Windows 11

### Issue Details

Chrome added the `Connection-Allowlist` response header - https://chromestatus.com/feature/5175745573945344
As far as I understand, it works similarly to `Content Security Policy` - https://github.com/WICG/connection-allowlists
Currently, when a website uses `Connection-Allowlist`, `local.adguard.org` gets blocked.
It should be shipped in Chrome 152 by default, but I can reproduce it in Chrome 151 already.

Steps to reproduce:
1. Add to user rules:
```adblock
usercontent.goog#%#console.log('AdGuard test message');
```
2. Navigate to https://safecontentframe.static.usercontent.goog/
3. Scroll to the bottom (to `Connection-Allowlist` section)
4. Open console
5. In `Connection Allowlist` section click on the `Render` button

### Expected Behavior

Message in console should be displayed.

### Actual Behavior

`local.adguard.org` is not added to `Connection Allowlist` response header, so it's blocked and message in console is not displayed.

Screenshot

Image

### Screenshots

_No response_

### Additional Information

_No response_

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。