Portal settings

From Sense/Net Wiki
Jump to: navigation, search
  •  
  •  
  •  
  •  
  • 100%
  • 6.3
  • Enterprise
  • Community
  • Planned

Overview

Portal settings

In Sense/Net ECMS there are many settings that control the behavior of the portal or the Content Repository. Some of these can be set in the Web.config file, others are stored as setting content in the database. Please check the main Settings article for more details on how this works. This article lists the settings that are related to the portal layer and stored in the database. The portal setting content can be found on the following path:

  • /Root/System/Settings/Portal.settings

Cache control headers

For detailed explanation of the cache control headers feature, please visit the Proxy Cache Configuration article. In the portal settings content you can define the rules that apply when the portal sets the MaxAge response header value for a particular content.

ClientCacheHeaders

The ClientCacheHeaders setting is a list of rules that define the MaxAge value for a set of content. Each rule must contain at least one of the following conditions:

  • ContentType: specific content type name
  • Path: path of a subtree
  • Extension: image or source file extension (e.g. jpg, css)

You can set more than one condition for a rule. In that case only those content will get that MaxAge value that satisfy all of the conditions for the rule. When a request arrives for a content and a MaxAge value must be set, the system starts to enumerate these rules, and the first match will be used. This means if you plan to define a complex set of rules (e.g. special values for content of custom type in certain folders), you have to place the most specific rules at the beginning, and the more general ones at the end.

BinaryHandlerClientCacheMaxAge

You can set the MaxAge value for all binaries requested through binaryhandler.ashx. The value must be provided in seconds.

<add key="BinaryHandlerClientCacheMaxAge" value="600" />

Example

The following example demonstrates how can you define the following rules:

  • custom value for a custom image type in a special folder
  • custom value for the same image type anywhere else
  • custom values for images and text files
<ClientCacheHeaders>    
  <CacheHeader ContentType="CustomImageType" Path="/Root/MyCustomFolder1" MaxAge="10"/>
  <CacheHeader ContentType="CustomImageType" MaxAge="3600"/>
  <CacheHeader Extension="jpeg" MaxAge="604800"/>
  <CacheHeader Extension="gif" MaxAge="604800"/>
  <CacheHeader Extension="jpg" MaxAge="604800"/>
  <CacheHeader Extension="png" MaxAge="604800"/>
  <CacheHeader Extension="css" MaxAge="600"/>
  <CacheHeader Extension="js" MaxAge="600"/>
  <CacheHeader/>
</ClientCacheHeaders>

UploadFileExtensions

BinaryHandlerClientCacheMaxAge

PermittedAppsWithoutOpenPermission

BreadCrumbBlackList

Defines a simple type filter for the BreadCrumb portlet. The navigation step will not appeared if the type of the content representation is blacklisted. The setting name is "BreadCrumbBlackList", value type is string array that contains case sensitive content type names. Example:

{
    ....
    BreadCrumbBlackList: ["ProjectWorkspaceFolder", "DocumentWorkspaceFolder", "SalesWorkspaceFolder"]
}

Related links

References

There are no related external articles for this article.