HTTP Response Policy

HTTP response policies evaluate responses from the server, and can be used to modify the server’s response headers. These policies are generally used to rewrite redirects or used in conjunction with HTTP request policies to provide a client to server name rewriting capability similar to Apache’s ProxyPass. If the intent is to create a hostname mapping from internal to external, consider using the more straightforward Host Name Translation feature within the advanced section of a virtual service. During the HTTP response match, the match criteria that are based on client data are evaluated against the original client request. For instance, if the client requested /fruit.htm, and a request policy modified the path to /cheese.htm, the response match rule for path would compare against the unmodified, original path sent from the client, /fruit.htm. The table below lists the match criteria available under HTTP response, as well as the actions that can be configured to occur upon a match being made.

Match Client IP: Client IP address or a group of client addresses.

  • Use a "-" to specify a range:
  • Use a "/" to specify a netmask:
  • Use a pre-defined IP group, which can be based on geo-location.
Service Port: The ports the virtual service is listening on.
Protocol Type: HTTP or HTTPS. Example:
HTTP Method: The method used by the client request. The match is true if any one of the methods that an administrator specifies is true.
HTTP Version: True if the client version is .9, 1.0, or 1.1
Path: The path or a group of paths. Paths start with a ‘/’. Example:
Query: A query or a group of queries. Do not add the leading ‘?’ or ‘&’ characters to a match. Example:
Headers: True if a header exists, or if it exists and contains a specified value
Cookie: True if a cookie exists, or if it exists and equals a specified value
Host Header: The request’s host header. Example:
Location Header: The location header may not exist for every website.
HTTP Status: The status of the response, such as 200 (success), 404 (file not found), or similar. The statuses can be separated by commas, or be a range. For example: 301, 302, 307, 308, 300-599
Response Header: Match based on a specific header sent by the server.
Actions Logging: Selecting the logging checkbox causes Vantage to log when an action has been invoked.
Modify Header: Allows for the addition, replacement, or removal of an HTTP header or cookie.
Rewrite Location Header: Changes the location header. Useful for proxying between internal and external names, such as to