This is the documentation for an older version of Scroll Viewport. Here you can view the most up-to-date version of the Scroll Viewport documentation.

Configuring Gobal Redirects

Scroll Viewport provides functionality for defining permanent and temporary redirects from one page to another. After reading this page, you should be able to maintain redirects.

Defining a New Redirect

Before you begin: To define a new redirect, you must log in with Confluence Admin permissions.

To define a new redirect:

  1. Click the cog icon at top right of the screen and select Confluence Admin.
    The Administration Console is displayed.
  2. In the Scroll Viewport section, click URL Redirects.
    The URL Redirects Management is displayed. The page consists of a table, showing all currently active redirects:

  3. Click Create to define a new redirect.
    The Create Redirect screen is displayed.

  4. Enter the following information:
    1. Enter an Incoming URL. At this point, you have three options:
      1. You can enter an absolute HTTP-addess - In this case, the redirect will only be applied if a request matches this addess exaclty.
      2. You can enter a path starting with "/" - Scroll Viewport will automatically prefix the path with your current Confluence baseUrl.
      3. In both cases you can use glob-pattern for covering a bigger range of incoming-URLs (see next chapter for more information). With glob-pattern you can use wildcard-characters. If you want to use in your incoming-URL, enable the checkbox.
    2. Enter the Target URL.
      (info) This is the URL, to which the user will be redirected if the redirect is being applied by Styles-Plugin. A Target-URL can either be an absolute or a path-based.
    3. In addition to that you can choose between different Redirect-Types. The following two redirect-types are available:
      1. 301 (Moved Permanently)
      2. 302 (Moved Temporarily)
  5. Click Save for saving and activating the redirect.

After completion, the newly created redirect should be listed in the table.


Here are some examples for defining Incoming- and Target-URLs:

Example 1 (absolute Incoming-URL):

Incoming URL =

In case of using an absolute Incoming URL,the redirect is only applied if the requested URL is fully equal to the entered Incoming URL.

Example 2 (path-based Incoming- and Target-URL):

Incoming URL = /Software/Scroll+Versions

Target URL = /software/scroll-versions/documentation

In this case, Scroll Viewport automatically prefixes the paths with the Confluence-baseUrl, so this is a short notation for absolute URLs.

Using a glob-pattern in your incoming URL

As previosly mentioned, you can use a regular expression for defining the Incoming URL. If enabled, each HTTP-Request will be matched against the regular expression.

  1. Use the text field Incoming URL for entering a regular expression.
  2. Enable the checkbox below for enabling regular expression matching.

Example 3 (glob-pattern-based Incoming-URL):

Incoming URL = /tutorial/**

Target URL = /dashboard.action

In this case, all pages existing under path /tutorial/ will be redirected to Confluence Dashboard.

Example 4 (blog-pattern-based Incoming-URL):

Incoming URL =**

In this case, all pages existing under path /Software/ will be matched and therefore become redirected. As opposed to the prior example, the homepage will also be matched here.

Example 5 (blog-pattern-based Incoming-URL):

Incoming-URL = /*/fragment

This Incoming URL will match for URLs which end on /fragment and are prefixed by an additional pathelement.