Files at the root of the Exago host install path (appSettings.config
), Web Service path (appSettings.config
), and scheduler install paths (eWebReportsScheduler.exe.config
) allow for some additional options to be set. These are xml files which host config options which need to be loaded by the web server at runtime.
Each .config
file is imported into its respective Web.config
file, which is the main settings file for each web application. Web.config
is automatically generated by Exago at each runtime, so any custom settings must be placed here instead.
If the relevant .config
file does not exist in an app directory, create it with the following data:
<?xml version="1.0"?>
<appSettings>
</appSettings>
To apply a setting, add an xml key in the <appSettings />
node with "key" and "value" parameter pairs, in the following form:
<add key="key" value="value" />
The following article is a collection of all the possible app settings, and descriptions for their use. In general, you should not use any of these settings unless you have been specifically directed by member of our support staff. Keys and values are case sensitive.
appSettings.config
Determine which method to use to store session information for the user's configuration. See Using "In-Memory" Session Storage for details.
Possible values:
Determine how aggressively to sanitize user-input data, such as report name, description, etc., against script attacks.
Possible values:
{webAppInstallDir}\Config\Other\tagwhitelist.json
Specifies the location of the WebReports.xml config file when storing the config in a Cloud (Azure/Amazon) location. See Installing Exago on Azure for details.
Set to false to disable the ability to append ?ShowErrorDetail=true
to an Exago URL to see the full text of error messages. See See Full Error Details for details.
Possible values:
(v2016.2.12+) Enable protection for Cross-Site Request Forgery (CSRF) attacks.
Possible values:
(v2016.2.12+) At specified intervals, during .NET Garbage Collection, Exago will attempt to compact the large object heap in order to reduce memory consumption by eliminating fragmentation. This will only happen in a .NET 4.5.1+ environment.
Possible values:
(v2016.3.4+) Specify which security protocol(s) the application should use. Multiple values are separated by commas (,).
Possible values (one or more):
(v2017.1+) Encompasses several keys determining which monitoring data is collected by the application. See Configuring Monitoring for details.
eWebReportsScheduler.exe.config
Specify the path & filename for the scheduler config file. Typically used in a multi-scheduler configuration where it would be desirable to maintain a global config file for all of them. If not specified, the scheduler will look for the config file in the default location.
(v2016.2.12+) At specified intervals, during .NET Garbage Collection, Exago will attempt to compact the large object heap in order to reduce memory consumption by eliminating fragmentation. This will only happen in a .NET 4.5.1+ environment.
Possible values:
(v2017.1+) Specify whether to collect data about the report executions handled by this scheduler.
Possible values:
Determine how aggressively to sanitize user-input data, such as report name, description, etc., against script attacks.
Possible values:
{schedulerInstallDir}\tagwhitelist.json
appSettings.config
Add this key to enable use of the REST Web Service API.
Possible values:
(v2016.3.4+) Specify which security protocol(s) the application should use. Multiple values are separated by commas (,).
Possible values (one or more):