In an SSL offload deployment, which rewrite action changes all occurrences of 'http://' in the HTTP response body to 'https://'?

• A. add rewrite action Act1 replace_all "HTTP.RES.BODY(200000)" "\"https://\"" pattern "http://" add rewrite policy Pol1 true Act1 NOREWRITE
• B. add rewrite action Act1 replace_all "HTTP.RES.BODY(200000)" "\"http:\"" pattern "https://\" add rewrite policy Pol1 true Act1 NOREWRITE
• C. add rewrite action Act1 replace_all "HTTP.RES.BODY(200000)" "\"https://\"" pattern "http://" add rewrite policy Pol1 true Act1 NOREWRITE
• D. add rewrite action Act1 replace_all "HTTP.RES.BODY(200000)" "\"https:\"" pattern "http://" add rewrite policy Pol1 true Act1 NOREWRITE

Answer: (C)

In an SSL offload setup, you want to ensure that any links or references coming back in the HTTP response body use HTTPS, not HTTP, so the client never switches to an insecure connection. To achieve this, you can rewrite the content of the response body by replacing all occurrences of http:// with https://.

The correct approach uses a rewrite action that targets the HTTP response body and performs a global replace. It specifies HTTP.RES.BODY(200000) as the input, replaces with the string https://, and searches for the pattern http://. The configuration escapes the replacement string as ""https://"" to ensure proper parsing, while the pattern is "http://". This means every http:// found in the response body will be replaced with https://, turning all links to secure ones in the client-visible content.

Other options either swap the replacement and the pattern, target a different part of the response (not the body), or use the wrong strings, so they wouldn’t convert http links to https in the body.