====== Subscriber Notifications (Service 6) ======
{{indexmenu_n>7}}
<note>[[en:dpi:dpi_options:opt_notify|Product Description]]</note>
<accordion autoclose>
<accordion-item title="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.
</accordion-item>

<accordion-item title="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:
<code bash>fdpi_ctrl del --service 6 --ip <ip or login></code>

**Example:**
<code bash>fdpi_ctrl del --service 6 --ip 192.168.0.1</code>

For this, you can use [[dpi:dpi_components:platform:subscriber_management:subsman_remote|Remote DPI Management]].
</accordion-item>

<accordion-item title="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: <code bash>Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache</code>
  - Add ''?'' to the ''ntf_server'' URL parameter — it will be different each time: <code bash>ntf_server=192.168.0.18/ntf?</code>

[[dpi:dpi_options:opt_notify:notify_conf|More about the]] ''[[dpi:dpi_options:opt_notify:notify_conf|ntf_server]]'' parameter.
</accordion-item>
</accordion>