Configuring the AppRules policy to perform HTTP Redirect

08/19/2021 45 20938

DESCRIPTION:

The App Rules (Application Firewall) feature in the SonicOS can perform HTTP redirect to another domain name. For example: When a user accesses www.google.com you can perform an HTTP redirect to www.yahoo.com.

RESOLUTION:

Resolution for SonicOS 6.5

This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.

Step 1: Creating a Match Object

In the SonicWall Management Interface, navigate to  Manage |Objects | Match Objects page and Click on "Add" button to create a new Match Object.

- Object Name: enter a name
- Match Object Type: select HTTP Host
- Match Type: Partial Match or Exact Match
- Content: Enter the desired domain name (E.g. google.com)
- Click Add to populate the entry in the List: section and when done click OK button.

Step 2: Creating an Action Object

In the SonicWall Management Interface, navigate to Manage |Objects | Action Objects page and Click on "Add" button to create a new Action Object.

- Action Name: enter a name
- Action: HTTP Redirect
- Content: Enter the desired domain name (Http://www.yahoo.com)

Important: Always include the Http:// (protocol) in the URL

- When done click OK button.

Step 3: Create an AppRules Policy

 In the SonicWall Management Interface, navigate to Manage | Rules | Application Control page and click on "Add" button to create a new AppControl Policy

- Policy Name: enter a name
- Policy Type: HTTP Client
- Service Destination: HTTP
- Match Object: Select the appropriate Match Object
- Action Object: Select the appropriate Action Object (Redirect)
- Connection Side: Client Side
- Direction: Basic (Incoming or Both)
- when done click OK button to add the policy. 

Please Note: Make sure you enable the Global option Enable App Rules and also the Enable option on the policy.

How to Test:

From a computer behind SonicWall try accessing the Website www.google.com and the web browser will be automatically redirected to www.yahoo.com web page.

In the SonicWall Log an entry will be created when HTTP Redirect is performed:

Resolution for SonicOS 6.2 and Below

The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.

Step 1: Creating a Match Object

In the SonicWall Management Interface, navigate to Firewall > Match Objects page and Click on "Add" button to create a new Match Object.

- Object Name: enter a name
- Match Object Type: select HTTP Host
- Match Type: Partial Match or Exact Match
- Content: Enter the desired domain name (E.g. google.com)
- Click Add to populate the entry in the List: section and when done click OK button.

Step 2: Creating an Action Object

In the SonicWall Management Interface, navigate to Firewall > Action Objects page and Click on "Add" button to create a new Action Object.

- Action Name: enter a name
- Action: HTTP Redirect
- Content: Enter the desired domain name (Http://www.yahoo.com)

Important: Always include the Http:// (protocol) in the URL

- When done click OK button.

Step 3: Create an AppRules Policy

In the SonicWall Management Interface, navigate to Firewall | App Rules page and click on "Add" button to create a new AppRules Policy

- Policy Name: enter a name
- Policy Type: HTTP Client
- Service Destination: HTTP
- Match Object: Select the appropriate Match Object
- Action Object: Select the appropriate Action Object (Redirect)
- Connection Side: Client Side
- Direction: Basic (Incoming or Both)
- when done click OK button to add the policy.

Please Note: Make sure you enable the Global option Enable App Rules and also the Enable option on the policy.

How to Test:

From a computer behind SonicWall try accessing the Website www.google.com and the web browser will be automatically redirected to www.yahoo.com web page.

In the SonicWall Log an entry will be created when HTTP Redirect is performed: