AdguardTeam
Display blocking reason for blocked HTTPS tunnel events in request details
Issue Details
In cases where AdGuard attempts to filter the HTTPS traffic of an application that does not allow the use of the CA certificate provided by AdGuard, blocked 'HTTPS tunnel' events appear in the log. The reason why the connection is blocked is unclear to users because it is not displayed in the request details.
For example, as shown in the screenshot
Proposed solution
Add an explanation of the blocking reason for this type of requests on the request details screen.
Alternative solution
No response
This option has a drawback - the user will not know about the problem until they start studying the filtering log. AdGuard v3 displayed notifications with a solution to the problem — even a novice user could restore the application's functionality if, for some reason, they enabled HTTPS filtering for the application and forgot about it or couldn't find a way to roll back the change (or didn't understand the connection between HTTPS filtering and the problem).
AdGuard v3 displayed notifications with a solution to the problem — even a novice user could restore the application's functionality if, for some reason, they enabled HTTPS filtering for the application and forgot about it or couldn't find a way to roll back the change (or didn't understand the connection between HTTPS filtering and the problem).
Of course, that's far superior UX (of which we'd welcome the return gladly), but this request seems more likely to actually be implemented (sooner?), so we'd be happy w/ this baby step, as it were, & 🙏🏾 for more.
This option has a drawback - the user will not know about the problem until they start studying the filtering log. AdGuard v3 displayed notifications with a solution to the problem — even a novice user could restore the application's functionality if, for some reason, they enabled HTTPS filtering for the application and forgot about it or couldn't find a way to roll back the change (or didn't understand the connection between HTTPS filtering and the problem).
I agree. I think we then should restore that notification don't you?
