Parameter:
HTTP_PRELOAD_FILTERSShort description: Specifies which DSAPI filters should be preloaded at HTTP startup – avoids longer load times on the first request.
Profile
Parameter | HTTP_PRELOAD_FILTERS |
Category | HTTP / Web |
Component | Server |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | Comma-separated DSAPI filter file names (no path) |
Description
DSAPI filters are normally loaded lazily – only when the first matching request arrives. On the first call, this can introduce several seconds of delay because libraries and configurations are read at runtime.
HTTP_PRELOAD_FILTERS lists the filters that the HTTP task should load immediately after startup. The HTTP pipeline is then fully equipped from the first request onwards, which is especially important for SSO/auth filters.Example configuration
HTTP_PRELOAD_FILTERS=domsaml.dll,iwaredir.dll
Notes & pitfalls
- Specify file names only (no path). The filters must be findable via the usual DSAPI search path.
- Order matters when filters build on each other – keep the same order as in the Server / Internet Site document.
- Changes require an HTTP restart (
tell http restart).
- Misspelled filters are reported as errors in
console.log; HTTP still starts, but the filter is inactive.