Dynamic pages

[dnesteryuk]

Example:

http://localhost/article/1
http://localhost/article/2
http://localhost/article/3

There should be an option to get dynamic pages out of the scope (They should not be tracked).

[dnesteryuk]

This issue is moved to the engine repo, it should be implemented there. Later there may be an admin part providing an interface for configuring the entire prediction solution. Initially, this task was created in the client repo, because some requests can be filtered on the client side. Hence, useless requests won't create needless load on the engine. However, the client-based filtering is possible even if the configuration is kept on the engine side. For example, the client may request the configuration from the engine, that configuration may include rules which should be applied to filter useless requests. Every client can fetch the configuration once and cache it in the browser.