Which policy will modify all URLs in the response body from http:// to https:// in an SSL offload deployment?

Which policy will modify all URLs in the response body from http:// to https:// in an SSL offload deployment?

• A. Use a rewrite action to replace http:// with https:// in the response body
• B. Use a rewrite action to replace https:// with http:// in the response body
• C. Use a responder policy to redirect all http responses to https
• D. Use an SSL bridge

Answer: (A)

In an SSL offload deployment, you terminate TLS at the device and can transform the content that the backend sends back. To ensure every link inside the response body uses the secure scheme, a rewrite action is used to modify the response content itself. This action can substitute http:// with https:// across the entire response body, so all embedded URLs become https without requiring client-side redirects or separate link-by-link changes. This approach directly updates the actual HTML (and other text payloads) delivered to the client, preventing mixed-content issues. Redirecting all http responses to https would send a 3xx redirect to the client, which changes how the client reaches the resource but does not rewrite URLs embedded inside the existing response body. Replacing https:// with http:// would undo security, and an SSL bridge focuses on TLS termination/re-encryption rather than altering the content of responses.

In an SSL offload deployment, you terminate TLS at the device and can transform the content that the backend sends back. To ensure every link inside the response body uses the secure scheme, a rewrite action is used to modify the response content itself. This action can substitute http:// with https:// across the entire response body, so all embedded URLs become https without requiring client-side redirects or separate link-by-link changes. This approach directly updates the actual HTML (and other text payloads) delivered to the client, preventing mixed-content issues.

Redirecting all http responses to https would send a 3xx redirect to the client, which changes how the client reaches the resource but does not rewrite URLs embedded inside the existing response body. Replacing https:// with http:// would undo security, and an SSL bridge focuses on TLS termination/re-encryption rather than altering the content of responses.