The tables in this document show the fields available for the Contents and Security rules property groups.
By default, only some of the fields are displayed. You can use the column selector () to add fields.
Contents is available from Associated items when you edit a content library.
The overview contains a list of the contents that are associated with the selected content library.
|The name of the object file.
|The location where the object is saved: \Content\<Content library name>\<file name>.
|The object's URL path: /content/<Content library name>/<file name>.
|File size (KB)
|The file size in kilobytes.
|The ID of the object.
|The Date and time when the object was created.
|The Date and time when the object was last modified.
By whom the object was modified.
There are potential security risks with cached content. Browsers may store a local cached copy of content received from web servers. Some browsers cache content accessed via HTTP/HTTPS. If sensitive information in application responses is stored in the local cache, this information can be retrieved by other users who have access to the same computer at a future time.
With content cache-controls, you can modify the cache behavior of the browser to prevent such risks.
|Name of the content cache-control.
Regular expression to filter out matching URLs to which the cache settings are applied:
(.*?) - matches everything
(resources|appcontent) - matches requests containing "resources" OR "appcontent" in the URI, for example:
For repository use the standard System.Text.RegularExpressions.Regex class. The comparison is made by :
regex = new Regex(contentCacheControl.Filter)
For hub it is the standard nodejs RegExp:
regex = new RegExp(contentCacheControl.Filter)
regex.test("/api/hub" + res.req.originalUrl);
|Maximum age for cached content to be included. The default value 3600 (seconds) can be edited.
Public, max-age: The cached response is sent without revalidation.
Public, must-revalidate, max-age=0: Requires a cache to revalidate stale responses before using a cached response.
Private, max-age: The cached response is sent without revalidation. All or part of the response message is intended for a single user and must not be cached by a shared cache.
Private, must-revalidate, max-age=0: A normally uncacheable response is cacheable, but requires a cache to revalidate stale responses before using a cached response. All or part of the response message is intended for a single user and must not be cached by a shared cache.
No-store: The response cannot be reused.
|ID of the object.
|Date and time when the object was created.
|Date and time when the object was last modified.
By whom the object was modified.
Before modifying the cache-controls
Please note the following before modifying cache control headers:
It is generally not recommended to manually alter the cache-control headers.
Make sure that you understand how the browser caching behavior is affected by the changes.
Prior to applying any changes in a production environment, evaluate the risks of the changes.
Linking a new content cache-control
The cache-control has no owner. It has a mandatory reference to a content library and will only affect resources in that library that match the regular expression in the regex filter setting.
Do the following:
In the QMC, open Content libraries.
Double-click the content library to which you want to add content cache-controls.
Under Associated items, open Content cache-controls.
Click Link new content cache control.
Fill in the fields.
name and regex filter are mandatory. maxAge is stated in seconds and can be edited.
See also: Configuring content cache-controls
User access is available from Associated items when you edit a resource.
The preview shows a grid of the target resources and the source users who have access to the selected items.
Depending on rights, you can either edit or view a user, a resource, or an associated rule.
Security rules is available from Associated items when you edit a content library. The overview contains a list of the security rules that are associated with the selected content library.
The Security rules property group contains the user condition properties.
The name of the security rule.
|The description of what the rule does.
The ID for the rule.
|The permitted actions for the rule.
Status values: Yes or No.
|The security rule context (QMC, Hub, or Both).
|The security rule type (Default, Read only, or Custom).
|The security rule conditions.
|The ID of the security rule.
|Date and time when the security rule was created.
|Date and time when the security rule was last modified.
By whom the security rule was modified.