Enforce Stronger Block Page Behavior
The Agentless Notification No Way Out feature strengthens enforcement when a block page is triggered. Instead of allowing you to dismiss notifications with a close button, this feature:
- Replaces the close button with a custom message.
- Redirects the entire page to the block page, leaving only two options: closing the tab or navigating backward.
This ensures you cannot bypass security controls and must exit restricted sessions.
Use Cases
Use Case 1: Prevent Bypass Attempts
You attempt to access restricted content, and a block page appears. Normally, you could dismiss the notification and continue browsing. With No Way Out, the close button is replaced with a message such as Please close this tab to continue. This ensures you cannot dismiss the notification and continue browsing restricted content.
Use Case 2: Provide Custom Messaging
Instead of a generic close button, your organization wants to display tailored guidance. For example, the block page may show This action is restricted. Please close the tab to proceed. This provides organization‑specific instructions that align with internal policies.
Configure No Way Out Globally
To enable the feature across all policies, add the following line:
meta = meta.Set("nowayout","Please close this tab to continue”)
Configure No Way Out Per Policy
To enable the feature for specific policies, add the following header before calling MWG.Block():
MWG.BlockHeaders.Add("x-mwg-block-nwo","Custom text goes here")
When both global and policy‑based configurations are present:
The policy‑based header string takes precedence over the global setting.