Which would be a reason to implement HTTP rewriting?

A primary reason to implement HTTP rewriting is to support SSL/TLS offloading and enforce secure connections. When FortiWeb terminates an HTTPS connection from a client and communicates with the back-end server over unencrypted HTTP, the server might generate responses containing absolute URLs with http://. A response rewriting rule can be configured to replace these http:// links with https:// in the response headers and body before forwarding the response to the client. This prevents mixed content warnings and ensures the user's session remains securely encrypted, which is a critical security function. This is often used in conjunction with a rule that redirects initial HTTP requests to HTTPS.

B. To implement load balancing.

Load balancing is a separate FortiWeb feature that distributes traffic across multiple back-end servers; it is not implemented using HTTP rewriting rules.

C. To replace a vulnerable element in a requested URL.

This task is primarily handled by FortiWeb's security inspection profiles, such as attack signatures or sanitization, which are designed to detect and block malicious patterns.

D. The original page has moved to a new URL.

This scenario is best handled by a standard HTTP 301/302 redirect, which is a specific redirection feature, not the broader function of rewriting content or URLs transparently.

1. FortiWeb™ Administration Guide Version 7.0.0

Page 424

Section: "Response Rewriting Rule".

The guide states: "You can configure a response rewriting rule to replace content in the response body. For example

when FortiWeb performs SSL offloading

the back-end web servers may return a response body containing HTTP links. You can configure a response rewriting rule to replace the HTTP links with HTTPS links." This directly supports the explanation for answer A.

2. FortiWeb™ Administration Guide Version 7.0.0

Page 428

Section: "HTTP to HTTPS Redirect".

This section describes the feature to "automatically redirect HTTP requests to HTTPS

" which is a direct implementation of the reason stated in answer A.

3. FortiWeb™ Administration Guide Version 7.0.0

Page 313

Section: "Server Load Balancing".

This section details the configuration of server pools for load balancing

confirming it is a distinct function from rewriting.