PingAccess

Adding rewrite response header rules

Add a rewrite response header rule, which converts the response header value returned by the site into a public-facing value.

This rule rewrites one of three response headers:

  1. Location

  2. Content-Location

  3. URI

For example, the server-facing Location response header includes a path that begins with /test-war/. Using the information configured in the rewrite response header rule, PingAccess rewrites http://private/test-war/ with a public-facing path such as:

http://public/path/

Before you begin

Confirm that you aren’t using the agent model. Rewrite response header rules aren’t available for agent deployments.

Steps

  1. Click Access, then go to Rules > Rules.

  2. Click Add Rule.

  3. In the Name field, enter a unique name up to 64 characters.

    Special characters and spaces are allowed.

  4. In the Type list, select Rewrite Response Header.

  5. If the target host needs to be explicitly defined, clear the Any Site Target Host checkbox.

    When you select the Any Site Target Host checkbox, PingAccess rewrites the response header URI if it contains a domain defined in a site’s target host list.

  6. If you clear the Any Site Target Host checkbox, enter the domain name used by the backend site in the Server-Facing URI field.

  7. In the Public Path field, enter a valid URI path that you want to write into the URI.

    This must be a valid Uniform Resource Identifier (URI) path, and it must begin and end with a forward slash (/).

    Example:

    /importantstuff/ or /

  8. Click Save.