Setting to enable the developer mode. If set to true, merging of resources such as JavaScript and CSS is disabled, so that each corresponding script and stylesheet will be rendered as a separate link. If set to false (the default), these resources will be merged during delivery and only a single link will be rendered to each type of resource.

Additionally, when developer mode is enabled, a developer mode indicator is rendered on the page, the livereload script is included, and missing resource bundle keys are highlighted.

Links to transformed images contain eTags in order to be unique if the image changes. If this property is set to true, the eTags do not only reflect the actual image data, but also the transformation settings like jpegQuality. This is useful for development purposes, if you want to see changes in the image transformation configuration immediately. But it makes link building very expensive, because the image data must always be streamed to compute the eTag that reflects the current settings. Therefore this flag should usually be false, esp. for production systems, where image transformation settings are changed rarely. If it is false, a CAE restart is required after changing the image transformation settings.

true if links to resources such as JavaScript and CSS should be generated to point to files in the application container (e.g. in modules under META-INF/resources/themes/) instead of the content repository.

Duration after which outdated transformed blobs should be removed from the cache. This value is used to set the cache control headers for transformed blobs in case they are requested but either yet unknown to this CAE instance or outdated meanwhile. Only takes effect if cae.single-node=false, otherwise a redirect to the latest version of the blob is returned.

Indicates whether this is a preview cae.

True when this is a "standalone" CAE in a servlet container serving requests directly or false when behind some URL rewriting reverse proxy (e.g. Apache).