A Redirect Action policy rule might not take effect under certain conditions

Products

• Mobility Threat Protection
• ProxySG Software - SGOS

Issue/Introduction

A Redirect Action in the policy rule might not take effect when certain conditions are present in the policy. Such conditions include:

- response.header.*
- response.x_header.*
- http.response.apparent_data_type
- Blue Coat Malware-Scanning Policy

For example, the following Web Access Layer does not take effect :

<Cache>
    response.x_header.x-Connection="123" cache(no)

<Proxy>
    url.host=www.bluecoat.com action.myredir(yes)

define action myredir
  redirect(302, "http://www.bluecoat.com(.*)", "https://www.bluecoat.com$(1)")
end

Resolution

To address the problem, we have introduced a new Action: request_redirect. This Action is currently available only in the Content Policy Language (CPL) and not in the Visual Policy Manager (VPM).

The example above should be updated to :

<Cache>
    response.x_header.x-Connection="123" cache(no)

<Proxy>
    url.host=www.bluecoat.com action.myredir(yes)

define action myredir
  request_redirect(302, "http://www.bluecoat.com(.*)", "https://www.bluecoat.com$(1)")
end

This Action is only available in :

- SG 5.5.7.1 and newer SG 5.5 versions.

- SG 6.2.7.1 and newer SG 6.2 versions

- SG 6.3.2.2 and newer SG 6.3 versions