Page History

...

When enabled, this setting allows the This feature helps to make sure you have real human customers and not bots visiting and browsing your ecommerce store based on their activity in a session. A session is created when a user first comes to your site. Their IP address is logged.   

When enabled, you can set up monitoring and restricting of incoming concurrent requests  to your site made by a unique IP addresses. Both page views and dynamic service request totals can be monitored. Threshold values for either or both can be set so that if the number of views/requests reach threshold values set per unique IP address, subsequent requests will be blocked. Such data are collected and can be viewed. Specific IP addresses can be excluded from being checkedaddress in a session. Monitoring is done by setting session maximum limits (threshold values) of:

• page views, and/or
• dynamic service requests.

When a maximum threshold value is reached, your site can be set to:

• deny new requests rightaway by showing a '503 server busy' error
• redirect them to a challenge page (a page with Google Capcha on it) they have to pass successfully. (NOTE - If using this option, the page must be created first.) Failure to pass this challenge will result in denial of new requests.  

When a unique IP address is restricted, they are logged. This data can be collected and viewed. You can also add specific IP addresses to a whitelist so they are excluded from being monitored and restricted. 

Configure Settings

1. In the CMS, navigate go to Settings → Settings → Feature Management → System → Request Monitoring and Restriction.
   
   
   
2. Toggle ON When the Enable Request Monitoring and Restriction is enabled. click Configure. (If this option Configure is not availabledisplayed, contact Commerce Vision to have the feature switched onswitch on this feature.)
   Click Configure.
    
3. In Request Monitoring Dynamic Service Count Threshold, enter the threshold number of value for dynamic service counts  above which the request is monitoredrequest numbers before monitoring the IP address. Default: 0 (off)
   
   
4. In Request Monitoring Page View Count Threshold, enter the threshold value for number of page view counts views before monitoring the request is monitoredIP address. Default: 0 (off)
   
   
5. In Total Request Initiate Challenge Threshold, enter the total number of requests by non-whitelisted unique IP addresses before the challenge is initiated. The challenge is a page with captcha, which the user has to completepass. 
   
   
6. In Total Request Terminate Challenge Threshold, enter the total number of requests before failed attempts at the challenge is stoppedCaptcha challenge the user can have. Default: 0 (off)
    
7. In Total Request Deny New Session Threshold, enter the threshold value above which will produce the '503 - server too busy' page.
    
8. In Request Monitoring Excluded IP Address, enter one or more whitelist IP addresses to be excluded from monitoring.  that can exceed the threshold values set for monitoring. E.g., you might have testing or development IP addresses you might want to exclude.  
   
   
9. In Challenge Page Content Before, (if using Challenge) enter the HTML code for the page together with the Captcha challenge that appears displayed after the challenge threshold has been is reached.  
   
   
10. In Challenge Page Content After, (if using Challenge), enter the HTML code for the page together with the Captcha challenge that appears displayed after the challenge threshold has been is reached.

Related help

...