As of ImageProcessor.Web v3.2.0 configuration outwith the
Web.Config file is not installed automatically.
Instead default configuration matching the values below is built into the system. To overwrite these settings install the nuget package:
By default ImageProcessor.Web will install references to its HttpModule within the applications
file. This allows the library to intercept processing calls to locally stored image files.
Further configuration options can be enabled by installing the ImageProcessor.Web.Config
Nuget package which will add the additional configuration values to your
Details for these configuration values can be found below.
Contains setting pertaining to security configuration which allow the safe configuration of externally hosted files. The more precise the url, the more restrictive the whitelist.
Sources for image files are plugin based. That means by implementing the
IImageService interface and referencing the class in
configuration file you can add your own image sources.
This configuration setup was added in version v4.1.0. For versions prior to that the config is as follows.
Contains setting pertaining to caching configuration: Where to store the cache, how many days to store images for.
Sources for image caches are plugin based. That means by implementing the
IImageCache interface and referencing the class in
configuration file you can add your own image cache.
This configuration setup was added in version v4.2.0. For versions prior to that the config is as follows.
Contains information and configuration for all processors.
For security reasons as of ImageProcessor.Web v4.6.0 only the following essential processors are enabled by default.
Any others will have to to be manually enabled by adding the attribute
enabled="true" via the configuration.
Sources for image processors are plugin based. That means by implementing the
IWebGraphicsProcessor interfaces and referencing
the web implementaion in the configuration file you can add your own image processor.