DNSFilter
Create
Log in
Sign up
Roadmap
Feedback
Feature Requests
439
Changelog
Boards
Feature Requests
Known Issues
Powered by Canny
Feature Requests
Tell us what feature you’d love to see!
Details
Category
Select a category
Showing
Trending
Sort
Trending
Top
New
Filter
Not Pursuing
Later
Next
Now
More Information Needed
Launched
posts in
All Categories
All Categories
Roaming Clients (103)
RC - Windows (11)
RC - macOS (10)
RC - iOS (7)
RC - Android (10)
RC - Chrome (3)
Policy and Filtering (160)
Policy - Filtering (34)
Policy - New Categories (19)
Policy - AppAware (33)
Policy - Testing (3)
Policy - Block Page (35)
Policy - Allow and Block Lists (14)
Policy - URL Filtering (4)
Integrations (51)
Integrations - SIEM (8)
Integrations - Ticketing (2)
Integrations - Workflow (6)
Integrations - Alerting (4)
Integrations - Security (1)
Integrations - Authentication (3)
Integrations - RMM (3)
Integrations - Identity (3)
Reporting (82)
Reporting - Audit Log (4)
Reporting - Query Log (23)
Reporting - Result Validation (3)
Reporting - Scheduled Reports (10)
Reporting - Alerting (14)
Reporting - AppAware (3)
Reporting - Data Export (5)
Reporting - CyberSight (3)
Dashboard (60)
Dashboard - Mobile (2)
Dashboard - Configuration (25)
Dashboard - Authentication (7)
MSP Experience (53)
MSP - Tenant Management (17)
MSP - Reporting (15)
MSP - Integrations (3)
MSP - API (1)
Relay (16)
Relay - Configuration (3)
Relay - Deployment (5)
Connectivity (12)
Connectivity - DNS-over-HTTPS (5)
Role Based Access (RBAC) (9)
RBAC - Role Management (9)
Deployments (16)
Deployments - Collections (8)
Deployments - Sites (6)
API (4)
Billing (4)
Disable HTTPS block page responses
For public wifi networks, where systems will not have our SSL Root CA installed, an option for an operator to only respond on port 80 would allow blocking w/o SSL errors (Instead it will say connection refused)
2
·
more information needed
13
Powered by Canny