Andrey Meshkov

### Issue Details The user may want to control the state of IPv6 for the VPN network interface and we currently do not provide this capability. ### Proposed solution I...

Add "IPv6 interface" setting to Advanced settings

1

### Issue Details The user may want to control the state of IPv6 for the VPN network interface and we currently do not provide this capability. ### Proposed solution I...

### Issue Details Currently, it is basically has two states: * Auto -- when the setting is enabled, it is actually not enforced, but only added when the underlying network...

### Issue Details From what I am seeing, `content-script` requests takes ~100ms to load. For comparison, `userscripts` takes about 10ms so I assume the function that builds content script is...

Implement HTTP/3 outbound proxy

2

### Issue Details Currently, CoreLibs does not support filtering HTTP/3 proxies. The issue is similar to the HTTP/2 one: #1140 The difference is that HTTP/3 proxy support will also allow...

### Issue Details Currently, CoreLibs only partially uses cache as it ignores `If-Modified-Since` in the request headers. ### Proposed solution Here's what we should do: 1. Send `Last Modified` header...

Not all requests are reported to filtering log

1

### 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...

Add `$strict-first-party` modifier support

1

Here's the definition: https://adguard.com/kb/general/ad-filtering/create-own-filters/#strict-first-party-modifier Adding support for it should be relatively straightforward. Once it's added the documentation in the knowledge base should be updated.

See the details here: https://github.com/AdguardTeam/CoreLibs/issues/1927

Just like in other AdGuard products, we should automatically convert `:matches-path` to `[$path]` cosmetic rule modifier.