"<url-rewrite-rule_name>"

Enter the name of a new or existing rule. The maximum length is 63 characters.

To display the list of existing rules, enter:

edit ?

action {403-forbidden | redirect | redirect-301 | HTTP-request-body-rewrite | HTTP-response-body-rewrite | HTTP-header-rewrite | HTTP-response-header-rewrite}

Specify one of the following values:

• 403-forbidden—Send a 403 (Forbidden) response to the client.
• redirect—Send a 302 (Moved Temporarily) response to the client, with a new Location: field in the HTTP header.
• redirect-301—Send a 301 (Moved Permanently) response to the client, with a new Location: field in the HTTP header.
• HTTP-request-body-rewrite—Replace the specific HTTP content in the body of requests.
• HTTP-response-body-rewrite—Replace the specific HTTP content in the body of responses.
• HTTP-header-rewrite—Rewrite the host, referer and request URL fields in HTTP header.
• HTTP-response-header-rewrite—Rewrite the HTTP header or body in the response packet.

The following rows list the configurations when different actions are selected.

HTTP-header-rewrite

header-name "<header-name_str>"

header-value "<header-value_str>"

host {<server_fqdn> | <server_ipv4> | <host_pattern>}

Type the FQDN of the host, such as store.example.com, to which the request will be redirected. The maximum length is 256 characters.

This option is available only when host-status {enable | disable} is enabled.

This field supports back references such as $0 to the parts of the original request that matched any capture groups that you entered in reg-exp "<object_pattern>" for each object in the condition table. (A capture group is a regular expression, or part of one, surrounded in parentheses.)

Use $n (0 <= n <= 9) to invoke a substring, where n is the order of appearance of the regular expression, from left to right, from outside to inside, then from top to bottom.

For example, regular expressions in the condition table in this order:

(a)(b)(c(d))(e)

(f)

would result in invokable variables with the following values:

• $0—a
• $1—b
• $2—cd
• $3—d
• $4—e
• $5—f

host-status {enable | disable}

Enable to rewrite the Host: field or host name part of the Referer: field.

When disabled, the FortiWeb appliance preserves the value from the client’s request when rewriting it.

host-use-pserver {enable | disable}

Enable this when you have a server farm for server balance or content routing. In this case you do not know which server in the server farm the FortiWeb appliance will use. When FortiWeb processes the request, it sets the value for the actual host.

This option is available only when host-status {enable | disable} is enabled. Any setting you make for host is ignored.

url "<replacement-url_str>"

Enter the string, such as /catalog/item1, that will replace the request URL. The maximum length is 256 characters.

This option is available only when url-status {enable | disable} is enabled.

Do not include the name of the web host, such as www.example.com, nor the protocol, which are configured separately in host {<server_fqdn> | <server_ipv4> | <host_pattern>}.

Like host, this field supports back references such as $0 to the parts reg-exp "<object_pattern>" for each object in the condition table.

For an example, see the FortiWeb Administration Guide:

HTTPS://docs.fortinet.com/fortiweb/admin-guides

url-status {enable | disable}

Enable to rewrite the URL part of the request URL.

If you disable this option, the FortiWeb appliance preserves the value from the client’s request when it rewrites it.

referer-status {enable | disable}

referer-use-pserver {enable | disable}

Enable this when you have a server farm for server balance or content routing. In this case you do not know which server in the server farm the FortiWeb appliance will use. When FortiWeb processes the request, it sets the value for the actual referrer.

This option is available only when referer-status {enable | disable} is enabled. Any setting you make for referer "<referer-url_str>" is ignored.

referer "<referer-url_str>"

Enter the replacement value for the Referer: field in the HTML header. The maximum length is 256 characters.

This option is available only when referer-status {enable | disable} is enabled.

http-method-status {enable | disable}

Enable to replace the original HTTP methods in a request with the specified method.

http-method <string>

Specify the HTTP method to replace the original one.

Please avoid changing the method on the fly unless absolutely necessary. It is important to consider the potential implications and ensure that the server can handle the new method correctly.

status-code-status {enable | disable}

Enable to replace the original status code in a response with the specified code.

status-code <int>

request-replace-existing-headers {enable | disable}

response-replace-existing-headers {enable | disable}

request-remove-duplicate-headers {enable | disable}

If the system finds multiple items in the HTTP request that match your specified header name, enabling this option will remove all of them. However, if this option is disabled, only the first matching item will be removed.

response-remove-duplicate-headers {enable | disable}

If the system finds multiple items in the HTTP response that match your specified header name, enabling this option will remove all of them. However, if this option is disabled, only the first matching item will be removed.

location "<location_str>"

Enter the URL string that provides a location for use in a 301 or 302 HTTP redirection when the HTTP request matches. The maximum length is 256 characters.

location-status {enable | disable}

Enable to configure the location_replace.

location_replace "<location_str>"

Enter the replacement value for the Location: field in the HTTP header for the response. The maximum length is 256 characters.

header-response-status {enable | disable}

Enable to configure HTTP header insertion when the HTTP response matches.

response-header-name <string>

Type the Header name that you want to insert into the HTTP response. You can add up to 10 headers in the insertion list.

response-header-value <string>

Type the value of the Header field.

<entry_index>

The index number of the header removal item.

response-removel-header-name <string>

The name of the header that you want to remove. Up to 10 header names can be added in the removal list.

http-request-body-rewrite <string>

Enter the value that will replace matching HTTP content in the body of requests. The maximum is 256 characters.

http-response-body-rewrite <string>

Enter the value that will replace matching HTTP content in the body of responses. The maximum is 256 characters.

<entry_index>

object {HTTP-host | HTTP-reference | HTTP-url}

Select which part of the HTTP request to test for a match:

• HTTP-host
• HTTP-url
• HTTP-reference (the Referer: field)

If the request must match multiple conditions (for example, it must contain both a matching Host: field and a matching URL), add each object match condition to the condition table separately.

protocol-filter {enable | disable}

Enable if you want to match this condition only for either HTTP or HTTPS. Also configure waf url-rewrite url-rewrite-rule.

For example, you could redirect clients that accidentally request the login page by HTTP to a more secure HTTPS channel—but the redirect is not necessary for HTTPS requests.

As another example, if URLs in HTTPS requests should be exempt from rewriting, you could configure the rewriting rule to apply only to HTTP requests.

protocol {HTTP | HTTPS}

Select the protocol to use.

reg-exp "<object_pattern>"

Depending on your selection in object {HTTP-host | HTTP-reference | HTTP-url} and reverse-match {yes | no}, type a regular expression that defines either all matching or all non-matching Host: fields, URLs, or Referer: fields. Then, also configure reverse-match {yes | no}.

For example, for the URL rewriting rule to match all URLs that begin with /wordpress, you could enter ^/wordpress, then, in reverse-match {yes | no}, select no.

The pattern is not required to begin with a slash ( / ). The maximum length is 256 characters.

Note: Regular expressions beginning with an exclamation point ( ! ) are not supported. Instead, use reverse-match {yes | no}.

reverse-match {yes | no}

Indicate how to use reg-exp "<object_pattern>"when determining whether or not this URL rewriting condition has been met.

• no—If the regular expression does match the request object, the condition is met.
• yes—If the regular expression does not match the request object, the condition is met.
  The effect is equivalent to preceding a regular expression with an exclamation point ( ! ).

If all conditions are met, the FortiWeb appliance will do your selected action {403-forbidden | redirect | redirect-301 | HTTP-request-body-rewrite | HTTP-response-body-rewrite | HTTP-header-rewrite | HTTP-response-header-rewrite}.

content-filter {enable | disable}

content-type-set {text/html | text/plain | text/javascript | application/xml(or)text/xml | application/javascript | application/soap+xml | application/x-javascript | application/json | application/rss+xml | multipart/form-data | application/x-www-form-urlencoded}

Enter the HTTP content types that you want to match in a space-delimited list, such as:

set content-type-set text/html text/plain