Configuration profiles

Configuration profiles are a means to address a set of configuration properties through an alias. These profiles often represent standard use cases for some filter or servlet. Profiles can be used by specifying the name of the profile as value of the filter or servlet initialization parameter Profile. Several pre-defined profiles are already available (see the documentation of the individual filters and servlets).

Profiles can also be aggregated, as long as they do not overlap (i.e. a property is mentioned in both profiles). In the sample below, an InputValidationFilter for HTTP validation and limitation is configured using the two respective profiles.

<filter>
 <filter-name>HttpValidationFilter</filter-name>
 <filter-class>ch::nevis::isiweb4::filter::validation::InputValidationFilter</filter-class>
 <init-param>
  <param-name>Profile</param-name>
  <param-value>HTTP-Validation,HTTP-Limitations</param-value>
 </init-param>
</filter>

It is also possible to create customized profiles. You can define these in the bc.properties file or by using external properties files (set PROXY_CUSTOM_PROFILES= /path/to/your/custom.profiles.properties,/path/to/your/custom2.profiles.properties in env.conf). Take a look at the /opt/nevisproxy/<version>/etc/profiles.properties file, if you want to create custom profiles.

An attribute can be set as follows:

<classpath>.<classname>.<attribute>
<classpath>.<attribute>
<classpath>.<classname>.<profile>.<attribute>
<classpath>.<profile>.<attribute>