<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Actions on Webscale Product Documentation</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/</link><description>Recent content in Actions on Webscale Product Documentation</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.webscale.com/docs/reference/web-controls/actions/index.xml" rel="self" type="application/rss+xml"/><item><title>Add address to set</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/add-address-to-set/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/add-address-to-set/</guid><description>&lt;p&gt;This action adds the requester&amp;rsquo;s IP address to a dynamic address set for a defined period of time.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is available on both Request and Response web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Select address set:&lt;/strong&gt; The dynamic address set to which the requester&amp;rsquo;s IP address is added. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Expires:&lt;/strong&gt; The amount of time, in seconds, that the IP address remains in the set. By default, the expiration is selected from preset values using the &lt;strong&gt;Expires&lt;/strong&gt; slider. Enabling &lt;strong&gt;Custom time&lt;/strong&gt; lets you enter an exact number of seconds. The minimum expiration is &lt;code&gt;300&lt;/code&gt; seconds.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the requester&amp;rsquo;s IP address is added to the selected address set and remains in the set until the configured expiration elapses.&lt;/p&gt;</description></item><item><title>Add labels</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/add-labels/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/add-labels/</guid><description>&lt;p&gt;This action tags matching traffic with one or more custom labels, which can be used to classify and identify that traffic.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is available on both Request and Response web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Add label:&lt;/strong&gt; One or more labels to attach to matching traffic. At least one label is required. Each label must begin with a lowercase letter and may contain lowercase characters, numbers, underscores, and dashes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, each defined label is attached to the matching traffic. Labels do not modify the request or response; they tag the traffic for classification.&lt;/p&gt;</description></item><item><title>Cache override</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/cache-override/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/cache-override/</guid><description>&lt;p&gt;This action changes the cache-related headers that originate from the backend, letting you control how a matching resource is cached by Webscale and downstream caches.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Always cache:&lt;/strong&gt; Allows the resource to be cached by Webscale ADCs and any downstream caches, including web browsers. This also allows optimizations to be applied to the resource.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bypass cache:&lt;/strong&gt; Sets the &lt;code&gt;Cache-Control&lt;/code&gt; header to &lt;code&gt;no-cache&lt;/code&gt;, informing all downstream caches, including the browser, not to cache the resource. This also prevents any optimization of the resource.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Expiration:&lt;/strong&gt; Adds a &lt;code&gt;Cache-Control&lt;/code&gt; header that expires at a selected time. For a more specific expiration time, use the &lt;strong&gt;Custom&lt;/strong&gt; setting.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Custom:&lt;/strong&gt; Sets the contents of the &lt;code&gt;Cache-Control&lt;/code&gt; header value directly, used as-is when valid, in place of the value returned from the application server. Note that &lt;code&gt;max-age&lt;/code&gt; is measured in seconds.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy modifies the cache-related headers of the response according to the selected setting before the response is cached or returned to the client.&lt;/p&gt;</description></item><item><title>Challenge user</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/challenge-user/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/challenge-user/</guid><description>&lt;p&gt;This action presents the requester with a CAPTCHA challenge before the request is served. A user who has already passed the challenge is not challenged again.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;p&gt;No further configurations are necessary for this action.&lt;/p&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy responds to the requester with a CAPTCHA challenge. Once a user successfully completes the challenge, a validation cookie (&lt;code&gt;wspc&lt;/code&gt;) is set, and subsequent requests that present a valid cookie are not challenged again. When a challenge is served, the proxy responds immediately and no further web controls are evaluated for that request; a requester that has already validated is not challenged, and evaluation continues normally.&lt;/p&gt;</description></item><item><title>Continue</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/continue/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/continue/</guid><description>&lt;p&gt;This action allows the evaluation of subsequent web controls to continue in the order they are defined.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;p&gt;No further configurations are necessary for this action.&lt;/p&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, this action takes no operation on the request or response and allows evaluation to proceed to the next web control in the defined order. Because it is not a final action, any web controls that follow are still evaluated.&lt;/p&gt;</description></item><item><title>Deny request</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/deny-request/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/deny-request/</guid><description>&lt;p&gt;This action blocks a matching request and returns a specified HTTP status code with a response body.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is available on both Request and Response web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;HTTP status code:&lt;/strong&gt; The status code returned as a result of the deny action. This must be a value between &lt;code&gt;200&lt;/code&gt; and &lt;code&gt;599&lt;/code&gt;. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Response body:&lt;/strong&gt; The response body to send when the request is denied.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the request is blocked and the specified status code and response body are returned to the client. This is a final action, so it terminates the evaluation of the remaining web controls.&lt;/p&gt;</description></item><item><title>Disable RUM</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/disable-rum/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/disable-rum/</guid><description>&lt;p&gt;This action disables Real User Monitoring (RUM) for a matching request. No RUM beacon script is injected into the response.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;p&gt;No further configurations are necessary for this action.&lt;/p&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy suppresses the injection of the RUM beacon script that is otherwise added to HTML responses. The response is returned to the client without the monitoring script.&lt;/p&gt;</description></item><item><title>Disable session tracking</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/disable-session-tracking/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/disable-session-tracking/</guid><description>&lt;p&gt;This action disables Webscale session tracking for a matching request. No session-tracking cookies are added to the response.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;p&gt;No further configurations are necessary for this action.&lt;/p&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy does not add the cookies it otherwise uses to track a session across requests. Any session-tracking cookies that would normally be set on the response are suppressed.&lt;/p&gt;</description></item><item><title>Discontinue</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/discontinue/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/discontinue/</guid><description>&lt;p&gt;This action stops the proxy from evaluating any further web controls. It is typically used to finalize a set of non-final actions so that no subsequent web controls are applied.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;p&gt;No further configurations are necessary for this action.&lt;/p&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the actions defined alongside it are applied and evaluation then halts. This is a final action, so it terminates the evaluation of the remaining web controls.&lt;/p&gt;</description></item><item><title>Drop request</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/drop-request/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/drop-request/</guid><description>&lt;p&gt;This action silently drops a matching request. The connection is terminated without returning any HTTP response to the client.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;p&gt;No further configurations are necessary for this action.&lt;/p&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy drops the request by closing the connection, so the client receives no status code, headers, or body. For HTTP/2 requests, where the connection cannot be closed in the same manner, the request is denied with a &lt;code&gt;403&lt;/code&gt; status code instead. Requests dropped by this action are not logged. This is a final action, so it terminates the evaluation of the remaining web controls.&lt;/p&gt;</description></item><item><title>Inject HTML</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/inject-html/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/inject-html/</guid><description>&lt;p&gt;This action injects HTML from a microsite file into a response. The content is inserted immediately before the closing &lt;code&gt;&amp;lt;/head&amp;gt;&lt;/code&gt; tag whenever the response content type is &lt;code&gt;text/html&lt;/code&gt;.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Microsite:&lt;/strong&gt; The microsite containing the file to inject. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Path:&lt;/strong&gt; A &lt;a href="https://control.webscale.com/docs/api#:~:text=value%20template" target="_blank"&gt;value template&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
 used to specify the path to the file within the selected microsite. This field is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met and the response content type is &lt;code&gt;text/html&lt;/code&gt;, the content of the specified microsite file is inserted into the response document immediately before the closing &lt;code&gt;&amp;lt;/head&amp;gt;&lt;/code&gt; tag.&lt;/p&gt;</description></item><item><title>Redirect request</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/redirect-request/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/redirect-request/</guid><description>&lt;p&gt;This action responds to a matching request with an HTTP redirect to a specified location.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is available on both Request and Response web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;HTTP status code:&lt;/strong&gt; The redirect status code to return. The available options are &lt;code&gt;301 Moved permanently&lt;/code&gt;, &lt;code&gt;302 Temporary redirect&lt;/code&gt;, &lt;code&gt;303 See other&lt;/code&gt;, &lt;code&gt;305 Use proxy&lt;/code&gt;, &lt;code&gt;307 Temporary redirect (POST)&lt;/code&gt;, and &lt;code&gt;308 Permanent redirect&lt;/code&gt;. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Redirect location:&lt;/strong&gt; A &lt;a href="https://control.webscale.com/docs/api#:~:text=value%20template" target="_blank"&gt;value template&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
 expected to resolve to a valid value for the &lt;code&gt;Location&lt;/code&gt; header. This field is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy returns the specified redirect status code with the resolved location in the &lt;code&gt;Location&lt;/code&gt; header. This is a final action, so it terminates the evaluation of the remaining web controls.&lt;/p&gt;</description></item><item><title>Redirect using map</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/redirect-using-map/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/redirect-using-map/</guid><description>&lt;p&gt;This action redirects a matching request based on a predefined URL map. If the request URL is found in the map, the request is redirected to the mapped location.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;HTTP status code:&lt;/strong&gt; The redirect status code to return. The available options are &lt;code&gt;301 moved permanently&lt;/code&gt;, &lt;code&gt;302 temporary redirect&lt;/code&gt;, &lt;code&gt;303 see other&lt;/code&gt;, &lt;code&gt;305 use proxy&lt;/code&gt;, and &lt;code&gt;307 temporary redirect (POST)&lt;/code&gt;. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;URL map:&lt;/strong&gt; The URL map used to look up the redirect location for the request. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Preserve query:&lt;/strong&gt; When enabled, query parameters from the request are preserved in the redirect location, unless the location in the URL map specifies a query separator (&lt;code&gt;?&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the request URL is looked up in the selected URL map. If a matching entry is found, the proxy redirects the request to the mapped location using the specified status code. If the request URL is found in the map and a redirect occurs, this is a final action and terminates the evaluation of the remaining web controls. If no matching entry is found, the request proceeds and any remaining web controls are evaluated.&lt;/p&gt;</description></item><item><title>Restrict access</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/restrict-access/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/restrict-access/</guid><description>&lt;p&gt;This action restricts access to users who are members of one of a set of roles in the Webscale security system.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Add role:&lt;/strong&gt; One or more roles in the Webscale security system. A user must belong to at least one of these roles to be granted access. At least one role is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy grants the request only if the user is a member of one of the specified roles. Requests that are not authorized are redirected to the Webscale sign-in page for authentication. Once authenticated and authorized, the user is automatically redirected back to the original URL and is not required to authenticate with Webscale again for the time specified in the role definition.&lt;/p&gt;</description></item><item><title>Rewrite URL</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/rewrite-url/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/rewrite-url/</guid><description>&lt;p&gt;This action rewrites the incoming request URL before it is served. It is designed to modify the URL path and the query parameters.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;URL:&lt;/strong&gt; A &lt;a href="https://control.webscale.com/docs/api#:~:text=value%20template" target="_blank"&gt;value template&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
 expected to resolve to a valid URL. This field is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the request URL is replaced with the result of the evaluated template before the request is served. The rewrite is intended to change the path and query parameters only. If the URL scheme or hostname is modified, the resulting behavior is unspecified.&lt;/p&gt;</description></item><item><title>Route for verification</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/route-for-verification/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/route-for-verification/</guid><description>&lt;p&gt;This action routes a matching request to the application&amp;rsquo;s verifying deployment, when one is configured.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;p&gt;No further configurations are necessary for this action.&lt;/p&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met and a verifying deployment exists for the application, the request is directed to that deployment&amp;rsquo;s backend. This affects any subsequent &lt;strong&gt;Use alternate backends&lt;/strong&gt; action that specifies a cluster, as well as the application&amp;rsquo;s default cluster routing. If no verifying deployment is configured, the request proceeds normally.&lt;/p&gt;</description></item><item><title>Serve</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/serve/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/serve/</guid><description>&lt;p&gt;This action immediately serves a microsite resource in response to a matching request, using a specified status code.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is available on both Request and Response web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Status code:&lt;/strong&gt; The HTTP status code to return. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Microsite:&lt;/strong&gt; The microsite from which to serve the resource. If omitted, the default microsite configured for the application is used.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Path:&lt;/strong&gt; A &lt;a href="https://control.webscale.com/docs/api#:~:text=value%20template" target="_blank"&gt;value template&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
 used as the path to the resource within the selected microsite. This field is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy serves the resource at the specified path with the specified status code. If the resource does not exist in the microsite, the file &lt;code&gt;index.html&lt;/code&gt; is served instead, which is guaranteed to exist. This is a final action, so it terminates the evaluation of the remaining web controls.&lt;/p&gt;</description></item><item><title>Set content security policy</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/set-content-security-policy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/set-content-security-policy/</guid><description>&lt;p&gt;This action adds or overrides the &lt;code&gt;Content-Security-Policy&lt;/code&gt; response header for a matching response.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is available on both Request and Response web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Report only:&lt;/strong&gt; When enabled, the policy is applied in report-only mode. The directives are written to the &lt;code&gt;Content-Security-Policy-Report-Only&lt;/code&gt; response header instead of &lt;code&gt;Content-Security-Policy&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Add directive:&lt;/strong&gt; Adds a single Content Security Policy directive and its values. The available directives are &lt;strong&gt;Base URI&lt;/strong&gt;, &lt;strong&gt;Block all mixed content&lt;/strong&gt;, &lt;strong&gt;Child source&lt;/strong&gt;, &lt;strong&gt;Connect source&lt;/strong&gt;, &lt;strong&gt;Default source&lt;/strong&gt;, &lt;strong&gt;Font source&lt;/strong&gt;, &lt;strong&gt;Frame source&lt;/strong&gt;, &lt;strong&gt;Form action&lt;/strong&gt;, &lt;strong&gt;Frame ancestors&lt;/strong&gt;, &lt;strong&gt;Image source&lt;/strong&gt;, &lt;strong&gt;Media source&lt;/strong&gt;, &lt;strong&gt;Object source&lt;/strong&gt;, &lt;strong&gt;Sandbox&lt;/strong&gt;, &lt;strong&gt;Script source&lt;/strong&gt;, &lt;strong&gt;Style source&lt;/strong&gt;, &lt;strong&gt;Upgrade insecure requests&lt;/strong&gt;, and &lt;strong&gt;Worker source&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Import directives:&lt;/strong&gt; Imports a set of directives from an existing policy.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy sets the configured directives on the &lt;code&gt;Content-Security-Policy&lt;/code&gt; response header, or on the &lt;code&gt;Content-Security-Policy-Report-Only&lt;/code&gt; header when &lt;strong&gt;Report only&lt;/strong&gt; is enabled. The value of each directive is usually a list of source expressions, though a few directives take a boolean.&lt;/p&gt;</description></item><item><title>Set cookie</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/set-cookie/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/set-cookie/</guid><description>&lt;p&gt;This action adds a cookie to the response returned to the client.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Cookie name:&lt;/strong&gt; The name of the cookie to set. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cookie value:&lt;/strong&gt; The value to set for the cookie. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Path:&lt;/strong&gt; The path to which the cookie applies. The default path of &lt;code&gt;/&lt;/code&gt; applies the cookie to all requests; setting a path limits the action to requests that match that path.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Max-Age:&lt;/strong&gt; The time until the cookie expires, set as a number of seconds. The portal accepts a number of days, hours, minutes, or seconds and converts the total to seconds.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the cookie is added to the response in a &lt;code&gt;Set-Cookie&lt;/code&gt; header so that it is returned to the client. The same cookie is also added to the &lt;code&gt;Cookie&lt;/code&gt; header of the request forwarded to the backend server, replacing any existing cookie of the same name there.&lt;/p&gt;</description></item><item><title>Set pagespeed options</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/set-pagespeed-options/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/set-pagespeed-options/</guid><description>&lt;p&gt;This action controls the PageSpeed optimization applied to matching traffic and configures which optimization filters are used.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Enable:&lt;/strong&gt; Whether PageSpeed runs. &lt;strong&gt;Yes&lt;/strong&gt; enables PageSpeed processing, &lt;strong&gt;No&lt;/strong&gt; disables it, and &lt;strong&gt;Make no decision&lt;/strong&gt; leaves the existing behavior unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Filters:&lt;/strong&gt; The filters to enable when PageSpeed runs. The filters enabled by default are &lt;code&gt;add_head&lt;/code&gt;, &lt;code&gt;canonicalize_javascript_libraries&lt;/code&gt;, &lt;code&gt;combine_css&lt;/code&gt;, &lt;code&gt;convert_meta_tags&lt;/code&gt;, &lt;code&gt;extend_cache&lt;/code&gt;, &lt;code&gt;fallback_rewrite_css_urls&lt;/code&gt;, &lt;code&gt;flatten_css_imports&lt;/code&gt;, &lt;code&gt;inline_css&lt;/code&gt;, &lt;code&gt;inline_import_to_link&lt;/code&gt;, &lt;code&gt;inline_javascript&lt;/code&gt;, &lt;code&gt;insert_dns_prefetch&lt;/code&gt;, &lt;code&gt;rewrite_css&lt;/code&gt;, &lt;code&gt;rewrite_images&lt;/code&gt;, &lt;code&gt;rewrite_javascript&lt;/code&gt;, and &lt;code&gt;rewrite_style_attributes_with_url&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, PageSpeed optimization is applied to the response according to the &lt;strong&gt;Enable&lt;/strong&gt; setting and the selected filters.&lt;/p&gt;</description></item><item><title>Set request header</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/set-request-header/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/set-request-header/</guid><description>&lt;p&gt;This action sets an HTTP request header on the incoming request before it is sent to a backend server. An existing header of the same name is overridden.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Header:&lt;/strong&gt; The name of the header to set. Header names must conform to &lt;code&gt;RFC 7230&lt;/code&gt;. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Value:&lt;/strong&gt; A &lt;a href="https://control.webscale.com/docs/api#:~:text=value%20template" target="_blank"&gt;value template&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
 evaluated to set the header value. This field is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy sets the specified header on the request before it is forwarded to the backend server, replacing any existing value for that header.&lt;/p&gt;</description></item><item><title>Set request timeout</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/set-request-timeout/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/set-request-timeout/</guid><description>&lt;p&gt;This action sets the maximum amount of time a matching request may take to be served before it is timed out.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Timeout:&lt;/strong&gt; The number of seconds for which a request can be served before it times out. This must be an integer greater than 0. This field is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy applies the specified timeout to the request. If the request is not served within that number of seconds, it is returned with a &lt;code&gt;504&lt;/code&gt; status code.&lt;/p&gt;</description></item><item><title>Set response header</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/set-response-header/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/set-response-header/</guid><description>&lt;p&gt;This action sets an HTTP response header on the response before it is returned to a web browser. An existing header of the same name is overridden.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is available on both Request and Response web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Header:&lt;/strong&gt; The name of the header to set. Header names must conform to &lt;code&gt;RFC 7230&lt;/code&gt;. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Value:&lt;/strong&gt; A &lt;a href="https://control.webscale.com/docs/api#:~:text=value%20template" target="_blank"&gt;value template&lt;i class="ps-1 fa fa-external-link"&gt;&lt;/i&gt;&lt;/a&gt;
 evaluated to set the header value. This field is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the proxy sets the specified header on the response before it is returned to the client, overriding any value previously set by the backend server or the cache.&lt;/p&gt;</description></item><item><title>Substitute</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/substitute/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/substitute/</guid><description>&lt;p&gt;This action replaces specific strings within the request URL and its query parameters with alternate strings. Substitutions occur in the order they are listed.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Contains:&lt;/strong&gt; The string to find within the request URL. The match is case-sensitive and must be between 1 and 255 characters. This field is required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Replace:&lt;/strong&gt; The string to substitute in place of the matched &lt;strong&gt;Contains&lt;/strong&gt; value. It must be between 1 and 255 characters. This field is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, each &lt;strong&gt;Contains&lt;/strong&gt; string found in the request URL is replaced with its corresponding &lt;strong&gt;Replace&lt;/strong&gt; string, and the result is parsed as the new request URL. Because substitutions are applied in sequence, the output of one substitution can affect a later one.&lt;/p&gt;</description></item><item><title>Terminate HTTPS</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/terminate-https/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/terminate-https/</guid><description>&lt;p&gt;This action offloads HTTPS at the Webscale edge. Traffic received over HTTPS is decrypted at the Webscale ADCs and sent to the backend servers unencrypted.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;p&gt;No further configurations are necessary for this action.&lt;/p&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, HTTPS is terminated at the Webscale ADCs and the connection to the backend is made over unencrypted HTTP. This action applies only to a &lt;strong&gt;Use alternate backends&lt;/strong&gt; action within the same web control. If the &lt;strong&gt;Remote URL&lt;/strong&gt; of that action specifies a scheme, the scheme takes precedence and this action has no effect.&lt;/p&gt;</description></item><item><title>Use alternate backends</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/use-alternate-backends/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/use-alternate-backends/</guid><description>&lt;p&gt;This action routes a matching request to backend servers other than the application&amp;rsquo;s default. You must specify a cluster, a list of servers, or a hostname.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Cluster:&lt;/strong&gt; A cluster to which traffic is sent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Servers:&lt;/strong&gt; A list of server IP addresses to which traffic is sent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hostname:&lt;/strong&gt; A fully qualified domain name (FQDN) whose addresses are used as the backend servers to which traffic is sent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Direct:&lt;/strong&gt; When enabled, requests bypass the configured application proxies and connect directly to the destination.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Remote URL:&lt;/strong&gt; A URL that modifies attributes of the request sent to the backend, including the request URI, the use of HTTPS, the &lt;code&gt;Host&lt;/code&gt; header, SNI, and the port used.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Relative to:&lt;/strong&gt; A path prefix removed from the beginning of the request URI before the &lt;strong&gt;Remote URL&lt;/strong&gt; is processed. This is useful for routing requests to backend services that do not expect the prefix.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the request is routed to the specified cluster, servers, or hostname. The &lt;strong&gt;Remote URL&lt;/strong&gt; can further modify the scheme, host, SNI, port, and path used for the backend request, and &lt;strong&gt;Relative to&lt;/strong&gt; removes a path prefix before that processing occurs. This is a final action, so it terminates the evaluation of the remaining web controls.&lt;/p&gt;</description></item><item><title>Use serverless function</title><link>https://docs.webscale.com/docs/reference/web-controls/actions/use-serverless-function/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.webscale.com/docs/reference/web-controls/actions/use-serverless-function/</guid><description>&lt;p&gt;This action invokes a serverless function to process a matching request.&lt;/p&gt;
&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note:&lt;/div&gt;
&lt;p&gt;This web control action is only available on Request web controls.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="configuration"&gt;Configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Handler:&lt;/strong&gt; The serverless function handler to invoke. This field is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="behavior"&gt;Behavior&lt;/h2&gt;
&lt;p&gt;When the conditions of the web control are met, the request is processed by the configured serverless function handler. This is a final action, so it terminates the evaluation of the remaining web controls.&lt;/p&gt;</description></item></channel></rss>