The advanced plugin settings allow admins to tweak the behavior of Scroll Viewport. This article describes which settings are available, and how to change them.

View and change the advanced plugin settings

Some advanced plugin settings can be defined on the space level, some can be activated on the global level, and some can be activated on both. Refer to the Available settings table below to see the scope of the individual advanced settings.

To view and change the values of the advanced plugin settings on a global level, navigate to Confluence Administration > Scroll Runtime > Advanced Plugin Settings > Select Scroll Viewport in the top-right dropdown.

Available Settings:

KeyDescriptionAllowed ValuesDefault Value


Indicates that some tweaks are enabled that may help, if Confluence/Viewport is running behind an Apache front-end server with mod_proxy, that messes up the forwarded URL (Google for the code ProxyPass directive the nocanon flag).

From the Apache mod_proxy docs:

Normally, mod_proxy will canonicalize ProxyPassed URLs. But this may be incompatible with some backends, particularly those that make use of PATH_INFO. The optional 'nocanon' keyword suppresses this, and passes the URL path "raw" to the backend. Note that may affect the security of your backend, as it removes the normal limited protection against URL-based attacks provided by the proxy.


enableViewportInfoForSpaceAdminsIndicates that an info about Scroll Viewport should be displayed to space admins in spaces that have not yet a viewport configured.true/falsetrue


Indicates that performance logging is allowed. Note that in the current implementation clients still need to set the corresponding HTTP request header to trigger logging for a specific request.true/falsefalse

The old approach for generating page slugs had a few deficiencies if the page titles contained characters like question marks. Our new solution ensures that the page titles will always consist of simple characters that don't need any percent encoding. This should improve the looks of your URLs.

Of course we are aware of the fact that you might want to keep the old approach now that your page has already been indexed by search engines. We've added a plugin setting that let's you revert to the classic behavior.

Possible values:

  • classic - the old page slugs as created by Scroll Viewport 1.x
  • simple - the new page slugs

classic, simple


A global Runtime PluginSetting that allows administrators to control the amount of search results per page.


This property can be used to switch the HTTP response code for redirects when a user is redirected from the confluence UI to the Viewport. By default, Viewport sends a temporary redirect (HTTP 302), but this setting can be used to send permanent redirects (HTTP 301) instead.

Possible values are "302" and "301". The default value is "302". This is a global setting, it affects all Viewports in the Confluence instance.

301, 302302

Controls which space administrators can edit themes with Scroll Viewport. Confluence administrators can always edit themes, regardless of the value of this setting.

If a comma-separated list of group names is given, only space administrators who belong to one of these groups can edit themes.

If the special value '*' is given all space administrators can edit themes used for the viewports of their respective spaces. Likewise, if the setting is empty no space administrator can edit themes.

Any comma-separated list of group names or * or empty.*