Subscriber Notifications (Service 6)

Product Description

1. The 'Subscriber Notification' service does not deactivate after redirecting the subscriber, leading to constant redirection to the notification page from all non-https pages.

The reason for constant redirection to the notification page is that the DPI does not see the redirection to the www-site with the notification, so it does not reset the service state. For automatic reset, traffic to the www-server must pass through the DPI.

2. How can the logic of service removal be implemented on the web server if routing traffic through SSG is undesirable?

To reset the subscriber notification service on the web server after displaying the page, it is necessary to issue a command to the DPI:

fdpi_ctrl del --service 6 --ip <ip or login>

Example:

fdpi_ctrl del --service 6 --ip 192.168.0.1

For this, you can use Remote DPI Management.

3. Subscribers continue to see the 'information page' even though the fastDPI service is removed from the IP on the first access.

You need to disable caching of the page being redirected to.
Options:

On the web server:

Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache

Add ? to the ntf_server URL parameter — it will be different each time:
```
ntf_server=192.168.0.18/ntf?
```

More about the ntf_server parameter.