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
Which users, roles, groups, IP's are accessing the route the most
It would add settings for:
How big of a history to track for each route. Default: the last 200 accesses, 0 means unlimited
DB log or file log or both. Use radio buttons
Enable Throttle and deny spam attempts
Throttle threshold. Measured in attempts per minute
Maintenance page destination
Route denied page destination. This would be a default if one isn't set in the component inspector
Changes to Features:
Current enable switch becomes a enable restrictions switch
If only whitelist restrictions exist, then assume no one can access the page except those people who are whitelisted
If only blacklist restriction exist, then assume everyone can access the page (Except people who arent logged in) except for those people who are blacklisted.
Add features for:
Clear individual route logs
Clear all route logs
Only tracking a route without restricting it. Guest attempts should still be logged via IP. This could be used to thwart DDoS or hack attempts
Add a radio button set for putting a route into enabled, maintenance mode, or hidden mode. It will do nothing special on enabled. Maintenance: This will redirect to the maintenance page ONLY if you have access, otherwise you will go to the denied access page. Hidden: This will make it appear as if the page doesn't exist to all users except those logged into the backend.
Denying access if you cross the threshold in route attempts. This applies to ALL routes and not just a single route.
The text was updated successfully, but these errors were encountered:
Add a Route Access Log. This would track:
It would add settings for:
Changes to Features:
Add features for:
The text was updated successfully, but these errors were encountered: