Configuring Hit exception processing in the SessionArchiving.properties file

You can set parameters in the SessionArchiving.properties to add Hits for "Server or Resource Not Found" error exceptions.

About this task

Use the information here to learn how to add synthetic hits for "Server or Resource Not Found" error exception.

Procedure

  1. Access the SessionArchiving.properties file.
  2. Set the ADDHITSFOR_RESOURCESNOTFETCHED property to 1 to specify that "synthetic hits" will be added to the .lts to restrict access to the web in case of "Server or Resource Not Found" exceptions when trying to the host.

    All synthetic hits that are added have a status code 200 and status code text of OK in both the request and response files as the replay server does not recognize URL's with other status. If this behavior is not suited to your needs, then set ADDHITSFOR_RESOURCESNOTFETCHED to 0 to stop adding synthetic hits and thus the replay server tries to fetch resources not found within session during replay.