AdguardTeam / AdguardTeam/AdguardForAndroid

No indication that HTTPS filtering should not be enabled for an app

Offen
#4,407 4 Kommentare 3 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Feature request Priority: P4 TechAudit Voting
Vorherrschende Sprache
Keine Sprachdaten
Sterne
1.9k
Forks
121
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

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

- [X] I am running the latest version
- [X] I checked the documentation and found no answer
- [X] I checked to make sure that this issue has not already been filed

### AdGuard version

4.0 Nightly 39

### Environment

```markdown
- OS: Android 13
- Device: Xiaomi phone
```

### Root access

- [ ] Yes, I have it.

### What filters do you have enabled?

_No response_

### What Stealth Mode options do you have enabled?

_No response_

### Issue Details

Generally, AdGuard should indicate if there's an issue with an app because of which this or that feature cannot (or should not) be enabled.

Talking about HTTPS filtering, not every app supports it when the certificate is in the User store. In the previous version we indicated that there's an issue by showing a dialog that explained the situation and asked the user again.

In v4.0 we should further improve this approach and use it not just for HTTPS filtering, but for App management (routing), Ad blocking, etc.

* HTTPS filtered apps. We should indicate that filtering cannot (or should not) be enabled for an app. Internally, we have a list of apps that support HTTPS filtering, all others do not.
* App management -> HTTPS filtering switch (same thing as HTTPS filtered apps)
* App management -> Route traffic through AdGuard. Internally, we have a list of exceptions, the apps that we do not route through AdGuard by default. We usually also have an issue on Github about such an app and it would be nice to mention that issue in the warning text. There's also a low-level setting that should be taken into account.
* Filtered apps. The same thing as with "Route traffic", we have a list of exceptions internally for which AdGuard won't do content filtering. We also usually have a link to a Github issue that we could mention to the user.
* App management -> Content filtering (same thing as Filtered apps).

### Expected Behavior

_No response_

### Screenshots

_No response_

### Additional Information

_No response_

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.