Configuring the Responder feature with a Redirect Action
Configuring the Responder feature with a redirect option and use that to redirect a client from a particular subnet to a specific URL.
Summary
The Redirect action of the responder is used to redirect the client if a request meets certain conditions, before the request is sent to the back-end server.
The example in this section uses the responder to block access to the back-end server for clients originating from IP address subnet 222.222.X.X. It then redirects the client to the URL http://redirectURL. Notice that, except for choosing a Redirect action, the steps in the folloowing procedure are the same as for configuring a Respondwith action.
Configuring Redirect Actions
The following table describes the parameters you must configure to create a redirect action
| Parameter |
Description |
|---|---|
| Name | The name of the action. This is a mandatory parameter and cannot be changed. The action name must not exceed 31 characters. |
| Type | The type of responder action being configured. This parameter determines the behaviour of the responder action. You can choose to respond to the client or redirect the client elsewhere. Select the Redirect action type to generate an HTTP redirect to the URL configured in the target string. |
| Target |
This parameter contains the URL to the location the client should redirected to. |
The procedure below describes the steps to create a Redirect action that redirects the client to the URL http://redirectURL.
To create a responder action
- In the left pane of the NetScaler configuration utility, expand Protection Features, then expand Responder and click Actions.
The Responder Actions page appears in the right pane, as shown below.
- Click Add. The Create Responder Action dialog box appears.
- In the Name text box, type the name of the responder action, for example Action-Responder-2.
- Under Type, select Redirect.
- In the Target text area, type http://redirectURL.
- Click Create, then click Close. The responder action you created now appears in the Responder Actions page.
Comments (1)
Sep 18, 2008
Anonymous says:
Note that the redirect action responds with a 302 status code. This can have an ...Note that the redirect action responds with a 302 status code. This can have an adverse affect on search engine rankings. If this is an issue for your application then it's better to construct a responder action that performs a 301 rewrite as shown:
add responder action "301-Redirect" respondwith "\"HTTP/1.x 301 Moved Permanently\\r\nLocation: http://www.go-here-instead.com\\r\nConnection: close\\r\nCache-Control: no-cache\\r\nPragma: no-cache\\r\n\"" -bypassSafetyCheck NO
Add Comment