Content management system configuration
Contents
This section describes configuration files related to content and media handling
Media Serving
XP_HOME/config/com.enonic.xp.portal.cfg
Configure the portal behaviour.
media.public.cacheControl = public, max-age=31536000, immutable
media.private.cacheControl = private, max-age=31536000, immutable
media.contentSecurityPolicy =
media.contentSecurityPolicy.svg =
- media.public.cacheControl
-
Defines media (images, attachments)
Cache-Controlheader when media is cachable and accessible by Everyone. Default:public, max-age=31536000, immutable - media.private.cacheControl
-
Defines media (images, attachments)
Cache-Controlheader when media is cachable and not accessible by Everyone. Default:private, max-age=31536000, immutable - media.contentSecurityPolicy
-
Defines media (images, attachments)
Content-Security-Policyheader. Default:default-src 'none'; base-uri 'none'; form-action 'none' - media.contentSecurityPolicy.svg
-
Defines media (images, attachments)
Content-Security-Policyheader in cases when it isimage/svg+xmlmime type. Default:default-src 'none'; base-uri 'none'; form-action 'none'; style-src 'self' 'unsafe-inline' - legacy.attachmentService.enabled
-
Enables/Disables attachment service. Default
true- means Legacy Attachment Service is enabled. - legacy.imageService.enabled
-
Enables/Disables image service. Default
true- means Legacy Image Service is enabled. - legacy.httpService.enabled
-
Enables/Disables legacy HTTP service. Default
true- means Legacy HTTP Service is enabled. - asset.cacheControl
-
Defines assets cache-control header when asset is cachable. Default:
public, max-age=31536000, immutable
Image
XP_HOME/config/com.enonic.xp.image.cfg
Configure the image service behaviour.
scale.maxDimension = 8000
filters.maxTotal = 5
memoryLimit = 100mb
progressive = jpeg
- scale.maxDimension
-
Defines maximum dimension size (both height and width) when scaling is done. Default:
8000 - filters.maxTotal
-
Defines maximum total filters applied per call. Default:
25 - memoryLimit
-
Defines Heap memory limit for image processing. If the memory limit is reached, the Image Service will start to protect itself from being overwhelmed by additional requests. It does so by responding with an HTTP
429 Too Many Requestsstatus code to subsequent incoming requests. This memory limit acts as a soft cap rather than a hard limit. This means that the used memory can momentarily exceed the limit. The value is set in percentage of total Heap, or in memory units (mb,gb, …). Default:10% - progressive
-
Defines formats that will use progressive encoding. Default is
jpeg.
Binary Text Extractor
XP_HOME/config/com.enonic.xp.extractor.cfg
Configure binary text extractor service behaviour.
body.size.limit = 500000
- body.size.limit
-
Defines maximum number of characters from a textual media. Default:
500000
Content
XP_HOME/config/com.enonic.xp.content.cfg
Configure the content API behavior.
auditlog.enabled = true
- auditlog.enabled
-
Set to
falseto disable the creation of audit log entries on content API operations. Default:true.Audit log can be disabled by common enabledproperty. Content flag won’t affect anything in this case. - auditlog.filter
-
Comma separated values
rule(,rule)*of allow/deny rules. Default:!system.content.update,*(allow everything except "content update" event).
A rule prefixed with ! is a deny rule, otherwise it is an allow rule. A rule suffixed with * is a wildcard rule.
Rules are applied in sequence. A first matching rule wins. If no matching rule found, event type is denied. Only content event types can be filtered.
auditlog.filter = !*
auditlog.filter = *
auditlog.filter = !system.content.update,*
auditlog.filter = system.content.set*
- attachments.allowUnsafeNames
-
Set to
trueto allow suspicious characters in content attachment file names. Default:false. - resolveEmptyRegions
-
Set to
trueto use deprecated Content API functionality that will read Page/Layout descriptors and inject empty regions into fetched content objects. Default:false.
Setting resolveEmptyRegions to true can adversely impact system performance. By using this deprecated Content API functionality to read Page/Layout descriptors and inject empty regions into fetched content objects, additional computational resources and processing time are required. As such, it may lead to slower system response and reduced efficiency. Importantly, this functionality is deprecated and will be removed in future versions of Enonic XP. It is advisable to adapt your workflows to operate without this feature to ensure future compatibility. |