You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Later, I updated all the filters from the main home screen. When I opened a web browser and tried to open one of the IP addresses listed in the filter link (For Ex: 195.158.4.210), AG did not block this in the web browser perhaps due to unsupported filter rule syntax. Checking the 'Recent activity' confirmed no block on that IP address.
Proposed solution
In this case, it would be beneficial if AG immediately notifies the user after adding a filter that the filter is unsupported (displaying "Filter not supported" text in red) and prevents the user from enabling such a filter (by graying out the toggle switch for unsupported filters). Currently, the filter can be enabled, giving the impression that everything is 'fine' with that filter, when in reality, it is not effective.
Alternative solution
Manually check the compatibility of filters
The text was updated successfully, but these errors were encountered:
@Nzzyme unfortunately it is not possible to open or copy the filter link. Could you please re-send the link or email [email protected] with issue number 5512?
@Nzzyme unfortunately it is not possible to open or copy the filter link. Could you please re-send the link or email [email protected] with issue number 5512?
Issue Details
I added a custom IP filter by navigating to:
Settings > Filtering > Filters > Custom filters
Later, I updated all the filters from the main home screen. When I opened a web browser and tried to open one of the IP addresses listed in the filter link (For Ex: 195.158.4.210), AG did not block this in the web browser perhaps due to unsupported filter rule syntax. Checking the 'Recent activity' confirmed no block on that IP address.
Proposed solution
In this case, it would be beneficial if AG immediately notifies the user after adding a filter that the filter is unsupported (displaying "Filter not supported" text in red) and prevents the user from enabling such a filter (by graying out the toggle switch for unsupported filters). Currently, the filter can be enabled, giving the impression that everything is 'fine' with that filter, when in reality, it is not effective.
Alternative solution
Manually check the compatibility of filters
The text was updated successfully, but these errors were encountered: