For instance, say that the login.html page in your web site runs a few Java scripts that throw Object expected errors, which you want the eG agent to ignore. In this case, your error specification can be as follows: Object expected:http://www.eazykart.com/web/login.html. Alternatively, you can provide only that text string with which the error message begins in your specification – eg., Object:http://www.eazykart.com/web/login.html. Moreover, instead of the complete URL, you can specify just the name of the HTML/jsp/aspx page in which the error is to be ignored – example: Object:login.html.
Multiple error message-URL combinations can also be provided as a comma-separated list. The format of your specification will be:
For example, to ignore the Object expected and Uncaught TypeError errors in the login.html page, use the following specification:
Likewise, to ignore the Object expected error in the login.html page and the Uncaught TypeError in the validate.js file, your specification will be:
If you want to ignore the Uncaught TypeError across all the pages of the web site, your specification will be as follows:
- The error message should not contain any special characters – in particular, the ‘:’ (the colon) and the ‘,’ (the comma) characters should be avoided.
- The case of the actual error message and the one specified as part of your error specification should match. This is because, the eG agent performs case-sensitive pattern matching.