URL access and redirect rules enable you to customize access to your web application based on the URL requested. For example, you can configure a rule to control access to certain portions of your application, based on a business requirement – without changing the configuration on the application itself.
You can configure a rule for a URL match or a Hostname/IP match. If a match is found, the request is processed according to the configured action. You can configure a rule to take the following actions on incoming requests:
- Bypass security
Allow the request without requiring additional security. - Deny the request
Explicitly deny the request without further processing. - Redirect the request temporarily or permanently
This option informs the browser and search engines whether the resource is:- moved permanently to a new location – and the browser should not attempt to request the original location any more. (Status 301)
- only temporarily located somewhere else and the browser should continue requesting the resource's original location. (Status 302)
- Take no action
This option still enables you to see the rule match in the logs, even though no other action is taken. This can be helpful during policy development, for example, to check that you configured the URL correctly, without any typos, without having to switch the whole service to passive mode.
Note that your rules can include a maximum of one wildcard (*) character.
Redirect Details
A redirect URL can be either a:
- fully-qualified URL (
http://www.example.com/index.html) - full path (like
/index.html)
Optionally, append %s to the end of the URL to redirect to the domain specified, as shown in this example.
Setup
- Service:
http://www.example.com/index.html - Match:
/* - Redirect URL:
http://www.redirectexample.com%s
How it Works
- Incoming Request:
http://www.example.com/a.html - Redirects to:
http://www.redirectexample.com/a.html