Implementing Contextual Image Delivery
Implement Contextual Image Delivery (CID) for your organization by configuring the image transformation service. You can also use the CID Administration API and, if need be, import certificates for HTTPS access.
- Configuring aliases for image locations
You can create an alias for an image or image location (on disk or on the web). End users can then refer to the alias instead of to the actual location when they construct an image transformation URL. This not only makes life easier for your end users, it also allows you to change the locations of images without forcing your users to rewrite their URLs. - Excluding subfolders of alias file locations from use
In your cwd_engine_conf.xml, if your<sources>section contains a<urls>section that contains any entries that start with file:/// (that is, refer to a location on disk), then certain subfolders are excluded from use by default for security reasons. You may want to change this list of subfolders for custom security. - Managing an image transformation URL allowlist
By default, CID accepts any URL under http://localhost. During implementation, you may want to allow all such URLs (or even more), but once CID goes into production, it is advisable to restrict the URLs that a user can use to an allowlist of allowed URLs, which you can configure in cwd_engine_conf.xml. Trying to convert an image that does not match the allowlist results in a WARN log message and returns a 1 by 1 pixel transparent GIF. - Configuring Contextual Image Delivery caching
CID can cache both the images being transformed themselves, and the timestamps for those images. Configure caching to your liking by creating and editing a CID caching configuration file. - Securing the microservice with SSL
You may wish to secure your microservice using Secure Socket Layer (SSL), so that an HTTPS connection is required to interact with the service.