KBI 311817 Issue Addressed: Exclusion URLs In Argent Sentinel TEST Have No Effect On Firing Events For HTTP Errors


Argent Advanced Technology 5.1A-2001-A and below


Monday, 20 April 2020


When the Argent Sentinel Engine runs a Web Session script, the Engine fires Alerts when the script logic fails, such as clicking an element or link that is not there

The Engine also checks HTTP errors (404, 500, etc.) in the background

If the page contains elements that causes these HTTP errors and the script logic runs fine, the Engine can still opt to fire Events for such HTTP errors

These errors are generally not essential and can be optionally excluded

The setting is part of the TEST definition, as shown below

However, exclusion URLs have no effect on which HTTP errors should fire Events

The issue has been addressed in Argent AT 5.1A-2004-B

Technical Background

This was caused by a coding error

The Argent Sentinel Main Engine uses the same code as Argent Defender while the core (Script Recorder and Player) has been completely redone

The error format that is sent back from Chrome (Argent Defender) has been greatly changed compared to Internet Explorer (Argent Defender)

This broke the URL exclusion logic in the Main Engine


Upgrade to Argent Advanced Technology 5.1A-2004-B or above

For customers who cannot upgrade immediately, they can turn off HTTP error checking

As explained earlier, it is generally not essential to check these HTTP errors as the Web Session script defines the monitoring logic