Which approach CANNOT be used to redirect HTTP to HTTPS for a Virtual Service?

Question

Options

• ASelect the System-Secure-HTTP Application Profile
• BUse a Network Security Policy
• CWrite a Datascript
• DUse an HTTP Request Policy

• A
  92% (24)
• C
  4% (1)
• D
  4% (1)

Explanation

Selecting the System-Secure-HTTP Application Profile cannot redirect HTTP to HTTPS because this profile is designed to configure a virtual service to handle HTTPS/SSL traffic, not to redirect unencrypted requests - applying it makes the VS terminate SSL, but performs no redirect action on incoming HTTP connections.

Why the distractors are wrong (i.e., they CAN redirect):

• Option D (HTTP Request Policy): Supports a native "Redirect" action that sends HTTP clients a 301/302 response pointing to the HTTPS URL - the most straightforward method.
• Option C (DataScript): A Lua-based DataScript can call the redirect function (e.g., avi.http.redirect()) giving full programmatic control over the redirect logic.
• Option B (Network Security Policy): Can be configured with a redirect rule at the connection level to enforce HTTPS before the request is even processed by the application profile.

Memory tip: Think of Application Profiles as describing how a VS processes traffic that already arrives - they define behavior for traffic that matches, not what to do with traffic that shouldn't have arrived at all. Redirection is an action, which requires a Policy, Script, or Security Rule - not a Profile.

No community discussion yet for this question.