How to Create a Site Splice

A walkthrough on how to create a Site Splice using a Web Control

Web Controls enable site administrators to use pre-defined, pre-tested security or performance rulesets based on their e-commerce application, minimizing the need to discover, define, and maintain the rules themselves. You can create individual rules that match request conditions and execute a set of actions you define in your Webscale Control Panel.

Site Splice allows you to build a website from multiple sources, such as microsites, multiple backends, canned content, and more. Use the Use Alternate Backends Web Control action to configure Site Splice, and to rewrite the source URL for SEO or other purposes. Some common use cases for using Site Splice include loading assets from an Amazon S3 bucket, or using ImageEngine. Use Alternate Backend is a final action. Final actions always run last; the order of execution of other actions is unspecified and not necessarily in the order displayed.

Create the Use Alternate Backend action

After you’ve created the Condition for which this Web Control action applies, click + Add action to create an action for the new Web Control, which opens the Create Action dialog. To proceed, click Select an Action.

Webscale Create Action dialog in the control panel

A list of actions is now displayed. Select Use Alternate Backends to proceed.

Webscale Create Action dialog in the control panel, showing the **Use Alternate Backends** configuration

The configuration choices listed are:

  • Cluster - If you have any clusters defined for your application and wish to apply this web control for one of them, select the cluster here.
  • Servers/Hostname- To use an IP address, select Servers and enter the IP. To use a hostname or domain name, select Hostname and enter the domain name.
  • Show URL Mapping - Click Show URL Mapping to set this option. URL mapping allows you to change the request URL before a request is made to a backend server. Choices are:
    • Remote URL - Used to access backend servers. This URL may omit the scheme. If the scheme is set, then that scheme will be used to access the backend server regardless of the request scheme. When a hostname is provided in the URL, then it will be used instead of the request hostname. If a path is provided, the pathname requested from the backend server will be the path formed by joining the URL path and the request path. See the table below for examples.
    • Relative To - The path in the URL space of the application at which the resources obtained from the backend server are mapped. If the request url path does not begin with Relative To then the results may be unpredictable. The path mapping logically happens before any mapping performed by the Remote URL attribute. To sum up, anything added in the Relative To field will be removed from the URL when making the request to the alternate backend. See the table below for examples.

Remote URL Setting Examples

Request URL Remote URL Effective URL
https://example.com/page https://example.com/page
https://example.com/page /prefix https://example.com/prefix/page
https://example.com/page //althost.com/ https://althost.com/page
https://example.com/page //althost.com/prefix https://althost.com/prefix/page
https://example.com/page http://althost.com/prefix https://althost.com/prefix/page

Relative To Setting Examples

Request URL Relative to Effective path
/ /
/base /base
/base /base /
/base/page /base /page

Example Rule

An example showing an alternate backend rule whereby all jpg or png files will be loaded from ImageEngine is here:

Webscale Alternate Backend Example

Further Reading

Have questions not answered here? Please Contact Support to get more help.


Last modified October 2, 2020