@robinmordasiewicz/f5xc-terraform-mcp 3.5.0 → 3.6.0

package/dist/docs/resources/proxy.md

@@ -56,30 +56,30 @@ resource "f5xc_proxy" "example" {
 ### Spec Argument Reference
 
 -> **One of the following:**
-&#x2022; <a id="active-forward-proxy-policies"></a>[`active_forward_proxy_policies`](#active-forward-proxy-policies) - Optional Block<br>Active Forward Proxy Policies Type. Ordered List of Forward Proxy Policies active<br>See [Active Forward Proxy Policies](#active-forward-proxy-policies) below for details.
+&#x2022; <a id="active-forward-proxy-policies"></a>[`active_forward_proxy_policies`](#active-forward-proxy-policies) - Optional Block<br>Ordered List of Forward Proxy Policies active<br>See [Active Forward Proxy Policies](#active-forward-proxy-policies) below for details.
 
-<a id="connection-timeout"></a>&#x2022; [`connection_timeout`](#connection-timeout) - Optional Number  Defaults to `2000`  Specified in milliseconds<br>Connection Timeout. The timeout for new network connections to upstream server.  The (2 seconds)
+<a id="connection-timeout"></a>&#x2022; [`connection_timeout`](#connection-timeout) - Optional Number  Defaults to `2000`  Specified in milliseconds<br>The timeout for new network connections to upstream server.  The (2 seconds)
 
 -> **One of the following:**
-&#x2022; <a id="do-not-advertise"></a>[`do_not_advertise`](#do-not-advertise) - Optional Block<br>Enable this option
-<br><br>&#x2022; <a id="site-virtual-sites"></a>[`site_virtual_sites`](#site-virtual-sites) - Optional Block<br>Advertise Site or Virtual Site. This defines a way to advertise a VIP on specific sites
+&#x2022; <a id="do-not-advertise"></a>[`do_not_advertise`](#do-not-advertise) - Optional Block<br>Can be used for messages where no values are needed
+<br><br>&#x2022; <a id="site-virtual-sites"></a>[`site_virtual_sites`](#site-virtual-sites) - Optional Block<br>Defines a way to advertise a VIP on specific sites
 
 -> **One of the following:**
 &#x2022; <a id="dynamic-proxy"></a>[`dynamic_proxy`](#dynamic-proxy) - Optional Block<br>DynamicProxyType<br>See [Dynamic Proxy](#dynamic-proxy) below for details.
 <br><br>&#x2022; <a id="http-proxy"></a>[`http_proxy`](#http-proxy) - Optional Block<br>HTTP Connect Proxy. Parameters for HTTP Connect Proxy
 
-<a id="no-forward-proxy-policy"></a>&#x2022; [`no_forward_proxy_policy`](#no-forward-proxy-policy) - Optional Block<br>Enable this option
+<a id="no-forward-proxy-policy"></a>&#x2022; [`no_forward_proxy_policy`](#no-forward-proxy-policy) - Optional Block<br>Can be used for messages where no values are needed
 
 -> **One of the following:**
-&#x2022; <a id="no-interception"></a>[`no_interception`](#no-interception) - Optional Block<br>Enable this option
+&#x2022; <a id="no-interception"></a>[`no_interception`](#no-interception) - Optional Block<br>Can be used for messages where no values are needed
 
 -> **One of the following:**
-&#x2022; <a id="site-local-inside-network"></a>[`site_local_inside_network`](#site-local-inside-network) - Optional Block<br>Enable this option
-<br><br>&#x2022; <a id="site-local-network"></a>[`site_local_network`](#site-local-network) - Optional Block<br>Enable this option
+&#x2022; <a id="site-local-inside-network"></a>[`site_local_inside_network`](#site-local-inside-network) - Optional Block<br>Can be used for messages where no values are needed
+<br><br>&#x2022; <a id="site-local-network"></a>[`site_local_network`](#site-local-network) - Optional Block<br>Can be used for messages where no values are needed
 
 <a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block
 
-<a id="tls-intercept"></a>&#x2022; [`tls_intercept`](#tls-intercept) - Optional Block<br>Configuration for TLS interception. Configuration to enable TLS interception
+<a id="tls-intercept"></a>&#x2022; [`tls_intercept`](#tls-intercept) - Optional Block<br>Configuration to enable TLS interception
 
 ### Attributes Reference
 
@@ -93,27 +93,27 @@ In addition to all arguments above, the following attributes are exported:
 
 An [`active_forward_proxy_policies`](#active-forward-proxy-policies) block supports the following:
 
-<a id="policies-42e2f7"></a>&#x2022; [`forward_proxy_policies`](#policies-42e2f7) - Optional Block<br>Forward Proxy Policies. Ordered List of Forward Proxy Policies active<br>See [Forward Proxy Policies](#policies-42e2f7) below.
+<a id="policies-42e2f7"></a>&#x2022; [`forward_proxy_policies`](#policies-42e2f7) - Optional Block<br>Ordered List of Forward Proxy Policies active<br>See [Forward Proxy Policies](#policies-42e2f7) below.
 
 #### Active Forward Proxy Policies Forward Proxy Policies
 
 A [`forward_proxy_policies`](#policies-42e2f7) block (within [`active_forward_proxy_policies`](#active-forward-proxy-policies)) supports the following:
 
-<a id="name-c2d06e"></a>&#x2022; [`name`](#name-c2d06e) - Optional String<br>Name. When a configuration object(e.g. Virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. Route's) name
+<a id="name-c2d06e"></a>&#x2022; [`name`](#name-c2d06e) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. Route's) name
 
-<a id="namespace-63e125"></a>&#x2022; [`namespace`](#namespace-63e125) - Optional String<br>Namespace. When a configuration object(e.g. Virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. Route's) namespace
+<a id="namespace-63e125"></a>&#x2022; [`namespace`](#namespace-63e125) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. Route's) namespace
 
-<a id="tenant-e68ab4"></a>&#x2022; [`tenant`](#tenant-e68ab4) - Optional String<br>Tenant. When a configuration object(e.g. Virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. Route's) tenant
+<a id="tenant-e68ab4"></a>&#x2022; [`tenant`](#tenant-e68ab4) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. Route's) tenant
 
 #### Dynamic Proxy
 
 A [`dynamic_proxy`](#dynamic-proxy) block supports the following:
 
-<a id="dynamic-proxy-disable-dns-masquerade"></a>&#x2022; [`disable_dns_masquerade`](#dynamic-proxy-disable-dns-masquerade) - Optional Block<br>Enable this option
+<a id="dynamic-proxy-disable-dns-masquerade"></a>&#x2022; [`disable_dns_masquerade`](#dynamic-proxy-disable-dns-masquerade) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="dynamic-proxy-domains"></a>&#x2022; [`domains`](#dynamic-proxy-domains) - Optional List<br>Domains. A list of Domains to be proxied. Wildcard hosts are supported in the suffix or prefix form Supported Domains and search order: 1. Exact Domain names: `www.example.com.` 2. Domains starting with a Wildcard: \*.example.com. Not supported Domains: - Just a Wildcard: \* - A Wildcard and TLD with no root Domain: \*.com. - A Wildcard not matching a whole DNS label. E.g. \*.example.com and \*.bar.example.com are valid Wildcards however \*bar.example.com, \*-bar.example.com, and bar*.example.com are all invalid. Additional notes: A Wildcard will not match empty string. E.g. \*.example.com will match bar.example.com and baz-bar.example.com but not .example.com. The longest Wildcards match first. Only a single virtual host in the entire route configuration can match on \*. Also a Domain must be unique across all virtual hosts within an advertise policy
+<a id="dynamic-proxy-domains"></a>&#x2022; [`domains`](#dynamic-proxy-domains) - Optional List<br>List of Domains to be proxied. Wildcard hosts are supported in the suffix or prefix form Supported Domains and search order: 1. Exact Domain names: `www.example.com.` 2
 
-<a id="dynamic-proxy-enable-dns-masquerade"></a>&#x2022; [`enable_dns_masquerade`](#dynamic-proxy-enable-dns-masquerade) - Optional Block<br>Enable this option
+<a id="dynamic-proxy-enable-dns-masquerade"></a>&#x2022; [`enable_dns_masquerade`](#dynamic-proxy-enable-dns-masquerade) - Optional Block<br>Can be used for messages where no values are needed
 
 <a id="dynamic-proxy-http-proxy"></a>&#x2022; [`http_proxy`](#dynamic-proxy-http-proxy) - Optional Block<br>Dynamic HTTP Proxy Type. Parameters for dynamic HTTP proxy<br>See [HTTP Proxy](#dynamic-proxy-http-proxy) below.
 
@@ -125,43 +125,43 @@ A [`dynamic_proxy`](#dynamic-proxy) block supports the following:
 
 A [`http_proxy`](#dynamic-proxy-http-proxy) block (within [`dynamic_proxy`](#dynamic-proxy)) supports the following:
 
-<a id="dynamic-proxy-http-proxy-more-option"></a>&#x2022; [`more_option`](#dynamic-proxy-http-proxy-more-option) - Optional Block<br>Advanced OPTIONS. This defines various OPTIONS to define a route<br>See [More Option](#dynamic-proxy-http-proxy-more-option) below.
+<a id="dynamic-proxy-http-proxy-more-option"></a>&#x2022; [`more_option`](#dynamic-proxy-http-proxy-more-option) - Optional Block<br>Defines various OPTIONS to define a route<br>See [More Option](#dynamic-proxy-http-proxy-more-option) below.
 
 #### Dynamic Proxy HTTP Proxy More Option
 
 A [`more_option`](#dynamic-proxy-http-proxy-more-option) block (within [`dynamic_proxy.http_proxy`](#dynamic-proxy-http-proxy)) supports the following:
 
-<a id="policy-dc12bf"></a>&#x2022; [`buffer_policy`](#policy-dc12bf) - Optional Block<br>Buffer Configuration. Some upstream applications are not capable of handling streamed data. This config enables buffering the entire request before sending to upstream application. We can specify the maximum buffer size and buffer interval with this config. Buffering can be enabled and disabled at VirtualHost and Route levels Route level buffer configuration takes precedence<br>See [Buffer Policy](#policy-dc12bf) below.
+<a id="policy-dc12bf"></a>&#x2022; [`buffer_policy`](#policy-dc12bf) - Optional Block<br>Some upstream applications are not capable of handling streamed data. This config enables buffering the entire request before sending to upstream application. We can specify the maximum buffer size and buffer interval with this config<br>See [Buffer Policy](#policy-dc12bf) below.
 
-<a id="params-c9d1d2"></a>&#x2022; [`compression_params`](#params-c9d1d2) - Optional Block<br>Compression Parameters. Enables loadbalancer to compress dispatched data from an upstream service upon client request. The content is compressed and then sent to the client with the appropriate headers if either response and request allow. Only GZIP compression is supported. By default compression will be skipped when: A request does NOT contain accept-encoding header. A request includes accept-encoding header, but it does not contain “gzip” or “*”. A request includes accept-encoding with “gzip” or “*” with the weight “q=0”. Note that the “gzip” will have a higher weight then “*”. For example, if accept-encoding is “gzip;q=0,*;q=1”, the filter will not compress. But if the header is set to “*;q=0,gzip;q=1”, the filter will compress. A request whose accept-encoding header includes “identity”. A response contains a content-encoding header. A response contains a cache-control header whose value includes “no-transform”. A response contains a transfer-encoding header whose value includes “gzip”. A response does not contain a content-type value that matches one of the selected mime-types, which default to application/javascript, application/JSON, application/xhtml+XML, image/svg+XML, text/CSS, text/HTML, text/plain, text/XML. Neither content-length nor transfer-encoding headers are present in the response. Response size is smaller than 30 bytes (only applicable when transfer-encoding is not chunked). When compression is applied: The content-length is removed from response headers. Response headers contain “transfer-encoding: chunked” and do not contain “content-encoding” header. The “vary: accept-encoding” header is inserted on every response. GZIP Compression Level: A value which is optimal balance between speed of compression and amount of compression is chosen<br>See [Compression Params](#params-c9d1d2) below.
+<a id="params-c9d1d2"></a>&#x2022; [`compression_params`](#params-c9d1d2) - Optional Block<br>Enables loadbalancer to compress dispatched data from an upstream service upon client request. The content is compressed and then sent to the client with the appropriate headers if either response and request allow. Only GZIP compression is supported<br>See [Compression Params](#params-c9d1d2) below.
 
-<a id="errors-be4463"></a>&#x2022; [`custom_errors`](#errors-be4463) - Optional Block<br>Custom Error Responses. Map of integer error codes as keys and string values that can be used to provide custom HTTP pages for each error code. Key of the map can be either response code class or HTTP Error code. Response code classes for key is configured as follows 3 -- for 3xx response code class 4 -- for 4xx response code class 5 -- for 5xx response code class Value of the map is string which represents custom HTTP responses. Specific response code takes preference when both response code and response code class matches for a request
+<a id="errors-be4463"></a>&#x2022; [`custom_errors`](#errors-be4463) - Optional Block<br>Map of integer error codes as keys and string values that can be used to provide custom HTTP pages for each error code. Key of the map can be either response code class or HTTP Error code. Response code classes for key is configured as follows 3 -- for 3xx response code class 4 -- for 4xx
 
-<a id="pages-241bd8"></a>&#x2022; [`disable_default_error_pages`](#pages-241bd8) - Optional Bool<br>Disable Default Error Pages. Disable the use of default F5XC error pages
+<a id="pages-241bd8"></a>&#x2022; [`disable_default_error_pages`](#pages-241bd8) - Optional Bool<br>Disable the use of default F5XC error pages
 
-<a id="normalize-343080"></a>&#x2022; [`disable_path_normalize`](#normalize-343080) - Optional Block<br>Enable this option
+<a id="normalize-343080"></a>&#x2022; [`disable_path_normalize`](#normalize-343080) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="normalize-19a976"></a>&#x2022; [`enable_path_normalize`](#normalize-19a976) - Optional Block<br>Enable this option
+<a id="normalize-19a976"></a>&#x2022; [`enable_path_normalize`](#normalize-19a976) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="timeout-14c486"></a>&#x2022; [`idle_timeout`](#timeout-14c486) - Optional Number<br>Idle Timeout. The amount of time that a stream can exist without upstream or downstream activity, in milliseconds. The stream is terminated with a HTTP 504 (Gateway Timeout) error code if no upstream response header has been received, otherwise the stream is reset
+<a id="timeout-14c486"></a>&#x2022; [`idle_timeout`](#timeout-14c486) - Optional Number<br>The amount of time that a stream can exist without upstream or downstream activity, in milliseconds. The stream is terminated with a HTTP 504 (Gateway Timeout) error code if no upstream response header has been received, otherwise the stream is reset
 
-<a id="size-302702"></a>&#x2022; [`max_request_header_size`](#size-302702) - Optional Number<br>Maximum Request Header Size. The maximum request header size for downstream connections, in KiB. A HTTP 431 (Request Header Fields Too Large) error code is sent for requests that exceed this size. If multiple load balancers share the same advertise_policy, the highest value configured across all such load balancers is used for all the load balancers in question
+<a id="size-302702"></a>&#x2022; [`max_request_header_size`](#size-302702) - Optional Number<br>The maximum request header size for downstream connections, in KiB. A HTTP 431 (Request Header Fields Too Large) error code is sent for requests that exceed this size. If multiple load balancers share the same advertise_policy, the highest value configured across all such load balancers is used
 
-<a id="add-a872f8"></a>&#x2022; [`request_cookies_to_add`](#add-a872f8) - Optional Block<br>Add Cookies in Cookie Header. Cookies are key-value pairs to be added to HTTP request being routed towards upstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Request Cookies To Add](#add-a872f8) below.
+<a id="add-a872f8"></a>&#x2022; [`request_cookies_to_add`](#add-a872f8) - Optional Block<br>Cookies are key-value pairs to be added to HTTP request being routed towards upstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Request Cookies To Add](#add-a872f8) below.
 
-<a id="remove-411cd3"></a>&#x2022; [`request_cookies_to_remove`](#remove-411cd3) - Optional List<br>Remove Cookies from Cookie Header. List of keys of Cookies to be removed from the HTTP request being sent towards upstream
+<a id="remove-411cd3"></a>&#x2022; [`request_cookies_to_remove`](#remove-411cd3) - Optional List<br>List of keys of Cookies to be removed from the HTTP request being sent towards upstream
 
-<a id="add-3661bf"></a>&#x2022; [`request_headers_to_add`](#add-3661bf) - Optional Block<br>Add Request Headers. Headers are key-value pairs to be added to HTTP request being routed towards upstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Request Headers To Add](#add-3661bf) below.
+<a id="add-3661bf"></a>&#x2022; [`request_headers_to_add`](#add-3661bf) - Optional Block<br>Headers are key-value pairs to be added to HTTP request being routed towards upstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Request Headers To Add](#add-3661bf) below.
 
-<a id="remove-031e38"></a>&#x2022; [`request_headers_to_remove`](#remove-031e38) - Optional List<br>Remove Request Headers. List of keys of Headers to be removed from the HTTP request being sent towards upstream
+<a id="remove-031e38"></a>&#x2022; [`request_headers_to_remove`](#remove-031e38) - Optional List<br>List of keys of Headers to be removed from the HTTP request being sent towards upstream
 
-<a id="add-9ca95a"></a>&#x2022; [`response_cookies_to_add`](#add-9ca95a) - Optional Block<br>Add Set-Cookie Headers. Cookies are name-value pairs along with optional attribute parameters to be added to HTTP response being sent towards downstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Response Cookies To Add](#add-9ca95a) below.
+<a id="add-9ca95a"></a>&#x2022; [`response_cookies_to_add`](#add-9ca95a) - Optional Block<br>Cookies are name-value pairs along with optional attribute parameters to be added to HTTP response being sent towards downstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Response Cookies To Add](#add-9ca95a) below.
 
-<a id="remove-09fdc6"></a>&#x2022; [`response_cookies_to_remove`](#remove-09fdc6) - Optional List<br>Remove Cookies from Set-Cookie Headers. List of name of Cookies to be removed from the HTTP response being sent towards downstream. Entire set-cookie header will be removed
+<a id="remove-09fdc6"></a>&#x2022; [`response_cookies_to_remove`](#remove-09fdc6) - Optional List<br>List of name of Cookies to be removed from the HTTP response being sent towards downstream. Entire set-cookie header will be removed
 
-<a id="add-91639a"></a>&#x2022; [`response_headers_to_add`](#add-91639a) - Optional Block<br>Add Response Headers. Headers are key-value pairs to be added to HTTP response being sent towards downstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Response Headers To Add](#add-91639a) below.
+<a id="add-91639a"></a>&#x2022; [`response_headers_to_add`](#add-91639a) - Optional Block<br>Headers are key-value pairs to be added to HTTP response being sent towards downstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Response Headers To Add](#add-91639a) below.
 
-<a id="remove-8ec5bc"></a>&#x2022; [`response_headers_to_remove`](#remove-8ec5bc) - Optional List<br>Remove Response Headers. List of keys of Headers to be removed from the HTTP response being sent towards downstream
+<a id="remove-8ec5bc"></a>&#x2022; [`response_headers_to_remove`](#remove-8ec5bc) - Optional List<br>List of keys of Headers to be removed from the HTTP response being sent towards downstream
 
 #### Dynamic Proxy HTTP Proxy More Option Buffer Policy
 
@@ -239,7 +239,7 @@ A [`more_option`](#dynamic-proxy-http-proxy-more-option) block (within [`dynamic
 
 A [`https_proxy`](#dynamic-proxy-https-proxy) block (within [`dynamic_proxy`](#dynamic-proxy)) supports the following:
 
-<a id="dynamic-proxy-https-proxy-more-option"></a>&#x2022; [`more_option`](#dynamic-proxy-https-proxy-more-option) - Optional Block<br>Advanced OPTIONS. This defines various OPTIONS to define a route<br>See [More Option](#dynamic-proxy-https-proxy-more-option) below.
+<a id="dynamic-proxy-https-proxy-more-option"></a>&#x2022; [`more_option`](#dynamic-proxy-https-proxy-more-option) - Optional Block<br>Defines various OPTIONS to define a route<br>See [More Option](#dynamic-proxy-https-proxy-more-option) below.
 
 <a id="dynamic-proxy-https-proxy-tls-params"></a>&#x2022; [`tls_params`](#dynamic-proxy-https-proxy-tls-params) - Optional Block<br>Inline TLS Parameters. Inline TLS parameters<br>See [TLS Params](#dynamic-proxy-https-proxy-tls-params) below.
 
@@ -247,37 +247,37 @@ A [`https_proxy`](#dynamic-proxy-https-proxy) block (within [`dynamic_proxy`](#d
 
 A [`more_option`](#dynamic-proxy-https-proxy-more-option) block (within [`dynamic_proxy.https_proxy`](#dynamic-proxy-https-proxy)) supports the following:
 
-<a id="policy-5af133"></a>&#x2022; [`buffer_policy`](#policy-5af133) - Optional Block<br>Buffer Configuration. Some upstream applications are not capable of handling streamed data. This config enables buffering the entire request before sending to upstream application. We can specify the maximum buffer size and buffer interval with this config. Buffering can be enabled and disabled at VirtualHost and Route levels Route level buffer configuration takes precedence<br>See [Buffer Policy](#policy-5af133) below.
+<a id="policy-5af133"></a>&#x2022; [`buffer_policy`](#policy-5af133) - Optional Block<br>Some upstream applications are not capable of handling streamed data. This config enables buffering the entire request before sending to upstream application. We can specify the maximum buffer size and buffer interval with this config<br>See [Buffer Policy](#policy-5af133) below.
 
-<a id="params-013546"></a>&#x2022; [`compression_params`](#params-013546) - Optional Block<br>Compression Parameters. Enables loadbalancer to compress dispatched data from an upstream service upon client request. The content is compressed and then sent to the client with the appropriate headers if either response and request allow. Only GZIP compression is supported. By default compression will be skipped when: A request does NOT contain accept-encoding header. A request includes accept-encoding header, but it does not contain “gzip” or “*”. A request includes accept-encoding with “gzip” or “*” with the weight “q=0”. Note that the “gzip” will have a higher weight then “*”. For example, if accept-encoding is “gzip;q=0,*;q=1”, the filter will not compress. But if the header is set to “*;q=0,gzip;q=1”, the filter will compress. A request whose accept-encoding header includes “identity”. A response contains a content-encoding header. A response contains a cache-control header whose value includes “no-transform”. A response contains a transfer-encoding header whose value includes “gzip”. A response does not contain a content-type value that matches one of the selected mime-types, which default to application/javascript, application/JSON, application/xhtml+XML, image/svg+XML, text/CSS, text/HTML, text/plain, text/XML. Neither content-length nor transfer-encoding headers are present in the response. Response size is smaller than 30 bytes (only applicable when transfer-encoding is not chunked). When compression is applied: The content-length is removed from response headers. Response headers contain “transfer-encoding: chunked” and do not contain “content-encoding” header. The “vary: accept-encoding” header is inserted on every response. GZIP Compression Level: A value which is optimal balance between speed of compression and amount of compression is chosen<br>See [Compression Params](#params-013546) below.
+<a id="params-013546"></a>&#x2022; [`compression_params`](#params-013546) - Optional Block<br>Enables loadbalancer to compress dispatched data from an upstream service upon client request. The content is compressed and then sent to the client with the appropriate headers if either response and request allow. Only GZIP compression is supported<br>See [Compression Params](#params-013546) below.
 
-<a id="errors-01c21a"></a>&#x2022; [`custom_errors`](#errors-01c21a) - Optional Block<br>Custom Error Responses. Map of integer error codes as keys and string values that can be used to provide custom HTTP pages for each error code. Key of the map can be either response code class or HTTP Error code. Response code classes for key is configured as follows 3 -- for 3xx response code class 4 -- for 4xx response code class 5 -- for 5xx response code class Value of the map is string which represents custom HTTP responses. Specific response code takes preference when both response code and response code class matches for a request
+<a id="errors-01c21a"></a>&#x2022; [`custom_errors`](#errors-01c21a) - Optional Block<br>Map of integer error codes as keys and string values that can be used to provide custom HTTP pages for each error code. Key of the map can be either response code class or HTTP Error code. Response code classes for key is configured as follows 3 -- for 3xx response code class 4 -- for 4xx
 
-<a id="pages-9edd65"></a>&#x2022; [`disable_default_error_pages`](#pages-9edd65) - Optional Bool<br>Disable Default Error Pages. Disable the use of default F5XC error pages
+<a id="pages-9edd65"></a>&#x2022; [`disable_default_error_pages`](#pages-9edd65) - Optional Bool<br>Disable the use of default F5XC error pages
 
-<a id="normalize-780e38"></a>&#x2022; [`disable_path_normalize`](#normalize-780e38) - Optional Block<br>Enable this option
+<a id="normalize-780e38"></a>&#x2022; [`disable_path_normalize`](#normalize-780e38) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="normalize-a240ab"></a>&#x2022; [`enable_path_normalize`](#normalize-a240ab) - Optional Block<br>Enable this option
+<a id="normalize-a240ab"></a>&#x2022; [`enable_path_normalize`](#normalize-a240ab) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="timeout-1062ad"></a>&#x2022; [`idle_timeout`](#timeout-1062ad) - Optional Number<br>Idle Timeout. The amount of time that a stream can exist without upstream or downstream activity, in milliseconds. The stream is terminated with a HTTP 504 (Gateway Timeout) error code if no upstream response header has been received, otherwise the stream is reset
+<a id="timeout-1062ad"></a>&#x2022; [`idle_timeout`](#timeout-1062ad) - Optional Number<br>The amount of time that a stream can exist without upstream or downstream activity, in milliseconds. The stream is terminated with a HTTP 504 (Gateway Timeout) error code if no upstream response header has been received, otherwise the stream is reset
 
-<a id="size-620c3f"></a>&#x2022; [`max_request_header_size`](#size-620c3f) - Optional Number<br>Maximum Request Header Size. The maximum request header size for downstream connections, in KiB. A HTTP 431 (Request Header Fields Too Large) error code is sent for requests that exceed this size. If multiple load balancers share the same advertise_policy, the highest value configured across all such load balancers is used for all the load balancers in question
+<a id="size-620c3f"></a>&#x2022; [`max_request_header_size`](#size-620c3f) - Optional Number<br>The maximum request header size for downstream connections, in KiB. A HTTP 431 (Request Header Fields Too Large) error code is sent for requests that exceed this size. If multiple load balancers share the same advertise_policy, the highest value configured across all such load balancers is used
 
-<a id="add-1b5bcd"></a>&#x2022; [`request_cookies_to_add`](#add-1b5bcd) - Optional Block<br>Add Cookies in Cookie Header. Cookies are key-value pairs to be added to HTTP request being routed towards upstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Request Cookies To Add](#add-1b5bcd) below.
+<a id="add-1b5bcd"></a>&#x2022; [`request_cookies_to_add`](#add-1b5bcd) - Optional Block<br>Cookies are key-value pairs to be added to HTTP request being routed towards upstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Request Cookies To Add](#add-1b5bcd) below.
 
-<a id="remove-cfd658"></a>&#x2022; [`request_cookies_to_remove`](#remove-cfd658) - Optional List<br>Remove Cookies from Cookie Header. List of keys of Cookies to be removed from the HTTP request being sent towards upstream
+<a id="remove-cfd658"></a>&#x2022; [`request_cookies_to_remove`](#remove-cfd658) - Optional List<br>List of keys of Cookies to be removed from the HTTP request being sent towards upstream
 
-<a id="add-0332ff"></a>&#x2022; [`request_headers_to_add`](#add-0332ff) - Optional Block<br>Add Request Headers. Headers are key-value pairs to be added to HTTP request being routed towards upstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Request Headers To Add](#add-0332ff) below.
+<a id="add-0332ff"></a>&#x2022; [`request_headers_to_add`](#add-0332ff) - Optional Block<br>Headers are key-value pairs to be added to HTTP request being routed towards upstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Request Headers To Add](#add-0332ff) below.
 
-<a id="remove-606625"></a>&#x2022; [`request_headers_to_remove`](#remove-606625) - Optional List<br>Remove Request Headers. List of keys of Headers to be removed from the HTTP request being sent towards upstream
+<a id="remove-606625"></a>&#x2022; [`request_headers_to_remove`](#remove-606625) - Optional List<br>List of keys of Headers to be removed from the HTTP request being sent towards upstream
 
-<a id="add-dd9473"></a>&#x2022; [`response_cookies_to_add`](#add-dd9473) - Optional Block<br>Add Set-Cookie Headers. Cookies are name-value pairs along with optional attribute parameters to be added to HTTP response being sent towards downstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Response Cookies To Add](#add-dd9473) below.
+<a id="add-dd9473"></a>&#x2022; [`response_cookies_to_add`](#add-dd9473) - Optional Block<br>Cookies are name-value pairs along with optional attribute parameters to be added to HTTP response being sent towards downstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Response Cookies To Add](#add-dd9473) below.
 
-<a id="remove-5d52c7"></a>&#x2022; [`response_cookies_to_remove`](#remove-5d52c7) - Optional List<br>Remove Cookies from Set-Cookie Headers. List of name of Cookies to be removed from the HTTP response being sent towards downstream. Entire set-cookie header will be removed
+<a id="remove-5d52c7"></a>&#x2022; [`response_cookies_to_remove`](#remove-5d52c7) - Optional List<br>List of name of Cookies to be removed from the HTTP response being sent towards downstream. Entire set-cookie header will be removed
 
-<a id="add-db908d"></a>&#x2022; [`response_headers_to_add`](#add-db908d) - Optional Block<br>Add Response Headers. Headers are key-value pairs to be added to HTTP response being sent towards downstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Response Headers To Add](#add-db908d) below.
+<a id="add-db908d"></a>&#x2022; [`response_headers_to_add`](#add-db908d) - Optional Block<br>Headers are key-value pairs to be added to HTTP response being sent towards downstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Response Headers To Add](#add-db908d) below.
 
-<a id="remove-27e742"></a>&#x2022; [`response_headers_to_remove`](#remove-27e742) - Optional List<br>Remove Response Headers. List of keys of Headers to be removed from the HTTP response being sent towards downstream
+<a id="remove-27e742"></a>&#x2022; [`response_headers_to_remove`](#remove-27e742) - Optional List<br>List of keys of Headers to be removed from the HTTP response being sent towards downstream
 
 #### Dynamic Proxy HTTPS Proxy More Option Buffer Policy
 
@@ -355,13 +355,13 @@ A [`more_option`](#dynamic-proxy-https-proxy-more-option) block (within [`dynami
 
 A [`tls_params`](#dynamic-proxy-https-proxy-tls-params) block (within [`dynamic_proxy.https_proxy`](#dynamic-proxy-https-proxy)) supports the following:
 
-<a id="mtls-1872dc"></a>&#x2022; [`no_mtls`](#mtls-1872dc) - Optional Block<br>Enable this option
+<a id="mtls-1872dc"></a>&#x2022; [`no_mtls`](#mtls-1872dc) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="certificates-6f0e81"></a>&#x2022; [`tls_certificates`](#certificates-6f0e81) - Optional Block<br>TLS Certificates. Users can add one or more certificates that share the same set of domains. For example, domain.com and \*.domain.com - but use different signature algorithms<br>See [TLS Certificates](#certificates-6f0e81) below.
+<a id="certificates-6f0e81"></a>&#x2022; [`tls_certificates`](#certificates-6f0e81) - Optional Block<br>Users can add one or more certificates that share the same set of domains. For example, domain.com and \*.domain.com - but use different signature algorithms<br>See [TLS Certificates](#certificates-6f0e81) below.
 
-<a id="config-116b33"></a>&#x2022; [`tls_config`](#config-116b33) - Optional Block<br>TLS Config. This defines various OPTIONS to configure TLS configuration parameters<br>See [TLS Config](#config-116b33) below.
+<a id="config-116b33"></a>&#x2022; [`tls_config`](#config-116b33) - Optional Block<br>Defines various OPTIONS to configure TLS configuration parameters<br>See [TLS Config](#config-116b33) below.
 
-<a id="mtls-7179b9"></a>&#x2022; [`use_mtls`](#mtls-7179b9) - Optional Block<br>Clients TLS validation context. Validation context for downstream client TLS connections<br>See [Use mTLS](#mtls-7179b9) below.
+<a id="mtls-7179b9"></a>&#x2022; [`use_mtls`](#mtls-7179b9) - Optional Block<br>Validation context for downstream client TLS connections<br>See [Use mTLS](#mtls-7179b9) below.
 
 #### Dynamic Proxy HTTPS Proxy TLS Params TLS Certificates
 
@@ -411,71 +411,71 @@ A [`tls_params`](#dynamic-proxy-https-proxy-tls-params) block (within [`dynamic_
 
 A [`sni_proxy`](#dynamic-proxy-sni-proxy) block (within [`dynamic_proxy`](#dynamic-proxy)) supports the following:
 
-<a id="dynamic-proxy-sni-proxy-idle-timeout"></a>&#x2022; [`idle_timeout`](#dynamic-proxy-sni-proxy-idle-timeout) - Optional Number<br>Idle Timeout. The amount of time that a stream can exist without upstream or downstream activity, in milliseconds
+<a id="dynamic-proxy-sni-proxy-idle-timeout"></a>&#x2022; [`idle_timeout`](#dynamic-proxy-sni-proxy-idle-timeout) - Optional Number<br>The amount of time that a stream can exist without upstream or downstream activity, in milliseconds
 
 #### HTTP Proxy
 
 A [`http_proxy`](#http-proxy) block supports the following:
 
-<a id="http-proxy-enable-http"></a>&#x2022; [`enable_http`](#http-proxy-enable-http) - Optional Block<br>Enable this option
+<a id="http-proxy-enable-http"></a>&#x2022; [`enable_http`](#http-proxy-enable-http) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="http-proxy-more-option"></a>&#x2022; [`more_option`](#http-proxy-more-option) - Optional Block<br>Advanced OPTIONS. This defines various OPTIONS to define a route<br>See [More Option](#http-proxy-more-option) below.
+<a id="http-proxy-more-option"></a>&#x2022; [`more_option`](#http-proxy-more-option) - Optional Block<br>Defines various OPTIONS to define a route<br>See [More Option](#http-proxy-more-option) below.
 
 #### HTTP Proxy More Option
 
 A [`more_option`](#http-proxy-more-option) block (within [`http_proxy`](#http-proxy)) supports the following:
 
-<a id="http-proxy-more-option-buffer-policy"></a>&#x2022; [`buffer_policy`](#http-proxy-more-option-buffer-policy) - Optional Block<br>Buffer Configuration. Some upstream applications are not capable of handling streamed data. This config enables buffering the entire request before sending to upstream application. We can specify the maximum buffer size and buffer interval with this config. Buffering can be enabled and disabled at VirtualHost and Route levels Route level buffer configuration takes precedence<br>See [Buffer Policy](#http-proxy-more-option-buffer-policy) below.
+<a id="http-proxy-more-option-buffer-policy"></a>&#x2022; [`buffer_policy`](#http-proxy-more-option-buffer-policy) - Optional Block<br>Some upstream applications are not capable of handling streamed data. This config enables buffering the entire request before sending to upstream application. We can specify the maximum buffer size and buffer interval with this config<br>See [Buffer Policy](#http-proxy-more-option-buffer-policy) below.
 
-<a id="params-c32856"></a>&#x2022; [`compression_params`](#params-c32856) - Optional Block<br>Compression Parameters. Enables loadbalancer to compress dispatched data from an upstream service upon client request. The content is compressed and then sent to the client with the appropriate headers if either response and request allow. Only GZIP compression is supported. By default compression will be skipped when: A request does NOT contain accept-encoding header. A request includes accept-encoding header, but it does not contain “gzip” or “*”. A request includes accept-encoding with “gzip” or “*” with the weight “q=0”. Note that the “gzip” will have a higher weight then “*”. For example, if accept-encoding is “gzip;q=0,*;q=1”, the filter will not compress. But if the header is set to “*;q=0,gzip;q=1”, the filter will compress. A request whose accept-encoding header includes “identity”. A response contains a content-encoding header. A response contains a cache-control header whose value includes “no-transform”. A response contains a transfer-encoding header whose value includes “gzip”. A response does not contain a content-type value that matches one of the selected mime-types, which default to application/javascript, application/JSON, application/xhtml+XML, image/svg+XML, text/CSS, text/HTML, text/plain, text/XML. Neither content-length nor transfer-encoding headers are present in the response. Response size is smaller than 30 bytes (only applicable when transfer-encoding is not chunked). When compression is applied: The content-length is removed from response headers. Response headers contain “transfer-encoding: chunked” and do not contain “content-encoding” header. The “vary: accept-encoding” header is inserted on every response. GZIP Compression Level: A value which is optimal balance between speed of compression and amount of compression is chosen<br>See [Compression Params](#params-c32856) below.
+<a id="params-c32856"></a>&#x2022; [`compression_params`](#params-c32856) - Optional Block<br>Enables loadbalancer to compress dispatched data from an upstream service upon client request. The content is compressed and then sent to the client with the appropriate headers if either response and request allow. Only GZIP compression is supported<br>See [Compression Params](#params-c32856) below.
 
-<a id="http-proxy-more-option-custom-errors"></a>&#x2022; [`custom_errors`](#http-proxy-more-option-custom-errors) - Optional Block<br>Custom Error Responses. Map of integer error codes as keys and string values that can be used to provide custom HTTP pages for each error code. Key of the map can be either response code class or HTTP Error code. Response code classes for key is configured as follows 3 -- for 3xx response code class 4 -- for 4xx response code class 5 -- for 5xx response code class Value of the map is string which represents custom HTTP responses. Specific response code takes preference when both response code and response code class matches for a request
+<a id="http-proxy-more-option-custom-errors"></a>&#x2022; [`custom_errors`](#http-proxy-more-option-custom-errors) - Optional Block<br>Map of integer error codes as keys and string values that can be used to provide custom HTTP pages for each error code. Key of the map can be either response code class or HTTP Error code. Response code classes for key is configured as follows 3 -- for 3xx response code class 4 -- for 4xx
 
-<a id="pages-159caf"></a>&#x2022; [`disable_default_error_pages`](#pages-159caf) - Optional Bool<br>Disable Default Error Pages. Disable the use of default F5XC error pages
+<a id="pages-159caf"></a>&#x2022; [`disable_default_error_pages`](#pages-159caf) - Optional Bool<br>Disable the use of default F5XC error pages
 
-<a id="normalize-3090b6"></a>&#x2022; [`disable_path_normalize`](#normalize-3090b6) - Optional Block<br>Enable this option
+<a id="normalize-3090b6"></a>&#x2022; [`disable_path_normalize`](#normalize-3090b6) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="normalize-8562f8"></a>&#x2022; [`enable_path_normalize`](#normalize-8562f8) - Optional Block<br>Enable this option
+<a id="normalize-8562f8"></a>&#x2022; [`enable_path_normalize`](#normalize-8562f8) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="http-proxy-more-option-idle-timeout"></a>&#x2022; [`idle_timeout`](#http-proxy-more-option-idle-timeout) - Optional Number<br>Idle Timeout. The amount of time that a stream can exist without upstream or downstream activity, in milliseconds. The stream is terminated with a HTTP 504 (Gateway Timeout) error code if no upstream response header has been received, otherwise the stream is reset
+<a id="http-proxy-more-option-idle-timeout"></a>&#x2022; [`idle_timeout`](#http-proxy-more-option-idle-timeout) - Optional Number<br>The amount of time that a stream can exist without upstream or downstream activity, in milliseconds. The stream is terminated with a HTTP 504 (Gateway Timeout) error code if no upstream response header has been received, otherwise the stream is reset
 
-<a id="size-c24d2e"></a>&#x2022; [`max_request_header_size`](#size-c24d2e) - Optional Number<br>Maximum Request Header Size. The maximum request header size for downstream connections, in KiB. A HTTP 431 (Request Header Fields Too Large) error code is sent for requests that exceed this size. If multiple load balancers share the same advertise_policy, the highest value configured across all such load balancers is used for all the load balancers in question
+<a id="size-c24d2e"></a>&#x2022; [`max_request_header_size`](#size-c24d2e) - Optional Number<br>The maximum request header size for downstream connections, in KiB. A HTTP 431 (Request Header Fields Too Large) error code is sent for requests that exceed this size. If multiple load balancers share the same advertise_policy, the highest value configured across all such load balancers is used
 
-<a id="add-19fe20"></a>&#x2022; [`request_cookies_to_add`](#add-19fe20) - Optional Block<br>Add Cookies in Cookie Header. Cookies are key-value pairs to be added to HTTP request being routed towards upstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Request Cookies To Add](#add-19fe20) below.
+<a id="add-19fe20"></a>&#x2022; [`request_cookies_to_add`](#add-19fe20) - Optional Block<br>Cookies are key-value pairs to be added to HTTP request being routed towards upstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Request Cookies To Add](#add-19fe20) below.
 
-<a id="remove-14fff8"></a>&#x2022; [`request_cookies_to_remove`](#remove-14fff8) - Optional List<br>Remove Cookies from Cookie Header. List of keys of Cookies to be removed from the HTTP request being sent towards upstream
+<a id="remove-14fff8"></a>&#x2022; [`request_cookies_to_remove`](#remove-14fff8) - Optional List<br>List of keys of Cookies to be removed from the HTTP request being sent towards upstream
 
-<a id="add-1a07e4"></a>&#x2022; [`request_headers_to_add`](#add-1a07e4) - Optional Block<br>Add Request Headers. Headers are key-value pairs to be added to HTTP request being routed towards upstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Request Headers To Add](#add-1a07e4) below.
+<a id="add-1a07e4"></a>&#x2022; [`request_headers_to_add`](#add-1a07e4) - Optional Block<br>Headers are key-value pairs to be added to HTTP request being routed towards upstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Request Headers To Add](#add-1a07e4) below.
 
-<a id="remove-58b55a"></a>&#x2022; [`request_headers_to_remove`](#remove-58b55a) - Optional List<br>Remove Request Headers. List of keys of Headers to be removed from the HTTP request being sent towards upstream
+<a id="remove-58b55a"></a>&#x2022; [`request_headers_to_remove`](#remove-58b55a) - Optional List<br>List of keys of Headers to be removed from the HTTP request being sent towards upstream
 
-<a id="add-9fc6d2"></a>&#x2022; [`response_cookies_to_add`](#add-9fc6d2) - Optional Block<br>Add Set-Cookie Headers. Cookies are name-value pairs along with optional attribute parameters to be added to HTTP response being sent towards downstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Response Cookies To Add](#add-9fc6d2) below.
+<a id="add-9fc6d2"></a>&#x2022; [`response_cookies_to_add`](#add-9fc6d2) - Optional Block<br>Cookies are name-value pairs along with optional attribute parameters to be added to HTTP response being sent towards downstream. Cookies specified at this level are applied after cookies from matched Route are applied<br>See [Response Cookies To Add](#add-9fc6d2) below.
 
-<a id="remove-c6e6e0"></a>&#x2022; [`response_cookies_to_remove`](#remove-c6e6e0) - Optional List<br>Remove Cookies from Set-Cookie Headers. List of name of Cookies to be removed from the HTTP response being sent towards downstream. Entire set-cookie header will be removed
+<a id="remove-c6e6e0"></a>&#x2022; [`response_cookies_to_remove`](#remove-c6e6e0) - Optional List<br>List of name of Cookies to be removed from the HTTP response being sent towards downstream. Entire set-cookie header will be removed
 
-<a id="add-3fc2d5"></a>&#x2022; [`response_headers_to_add`](#add-3fc2d5) - Optional Block<br>Add Response Headers. Headers are key-value pairs to be added to HTTP response being sent towards downstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Response Headers To Add](#add-3fc2d5) below.
+<a id="add-3fc2d5"></a>&#x2022; [`response_headers_to_add`](#add-3fc2d5) - Optional Block<br>Headers are key-value pairs to be added to HTTP response being sent towards downstream. Headers specified at this level are applied after headers from matched Route are applied<br>See [Response Headers To Add](#add-3fc2d5) below.
 
-<a id="remove-738a4c"></a>&#x2022; [`response_headers_to_remove`](#remove-738a4c) - Optional List<br>Remove Response Headers. List of keys of Headers to be removed from the HTTP response being sent towards downstream
+<a id="remove-738a4c"></a>&#x2022; [`response_headers_to_remove`](#remove-738a4c) - Optional List<br>List of keys of Headers to be removed from the HTTP response being sent towards downstream
 
 #### HTTP Proxy More Option Buffer Policy
 
 A [`buffer_policy`](#http-proxy-more-option-buffer-policy) block (within [`http_proxy.more_option`](#http-proxy-more-option)) supports the following:
 
-<a id="disabled-107694"></a>&#x2022; [`disabled`](#disabled-107694) - Optional Bool<br>Disable. Disable buffering for a particular route. This is useful when virtual-host has buffering, but we need to disable it on a specific route. The value of this field is ignored for virtual-host
+<a id="disabled-107694"></a>&#x2022; [`disabled`](#disabled-107694) - Optional Bool<br>Disable buffering for a particular route. This is useful when virtual-host has buffering, but we need to disable it on a specific route. The value of this field is ignored for virtual-host
 
-<a id="bytes-b00d03"></a>&#x2022; [`max_request_bytes`](#bytes-b00d03) - Optional Number<br>Max Request Bytes. The maximum request size that the filter will buffer before the connection manager will stop buffering and return a RequestEntityTooLarge (413) response
+<a id="bytes-b00d03"></a>&#x2022; [`max_request_bytes`](#bytes-b00d03) - Optional Number<br>The maximum request size that the filter will buffer before the connection manager will stop buffering and return a RequestEntityTooLarge (413) response
 
 #### HTTP Proxy More Option Compression Params
 
 A [`compression_params`](#params-c32856) block (within [`http_proxy.more_option`](#http-proxy-more-option)) supports the following:
 
-<a id="length-c8573b"></a>&#x2022; [`content_length`](#length-c8573b) - Optional Number  Defaults to `30`<br>Content Length. Minimum response length, in bytes, which will trigger compression. The
+<a id="length-c8573b"></a>&#x2022; [`content_length`](#length-c8573b) - Optional Number  Defaults to `30`<br>Minimum response length, in bytes, which will trigger compression. The
 
-<a id="type-794ba2"></a>&#x2022; [`content_type`](#type-794ba2) - Optional List<br>Content Type. Set of strings that allows specifying which mime-types yield compression When this field is not defined, compression will be applied to the following mime-types: 'application/javascript' 'application/JSON', 'application/xhtml+XML' 'image/svg+XML' 'text/CSS' 'text/HTML' 'text/plain' 'text/XML'
+<a id="type-794ba2"></a>&#x2022; [`content_type`](#type-794ba2) - Optional List<br>Set of strings that allows specifying which mime-types yield compression When this field is not defined, compression will be applied to the following mime-types: 'application/javascript' 'application/JSON', 'application/xhtml+XML' 'image/svg+XML' 'text/CSS' 'text/HTML' 'text/plain' 'text/XML'
 
-<a id="header-2ffee9"></a>&#x2022; [`disable_on_etag_header`](#header-2ffee9) - Optional Bool<br>Disable On Etag Header. If true, disables compression when the response contains an etag header. When it is false, weak etags will be preserved and the ones that require strong validation will be removed
+<a id="header-2ffee9"></a>&#x2022; [`disable_on_etag_header`](#header-2ffee9) - Optional Bool<br>If true, disables compression when the response contains an etag header. When it is false, weak etags will be preserved and the ones that require strong validation will be removed
 
-<a id="header-925ccf"></a>&#x2022; [`remove_accept_encoding_header`](#header-925ccf) - Optional Bool<br>Remove Accept-Encoding Header. If true, removes accept-encoding from the request headers before dispatching it to the upstream so that responses do not GET compressed before reaching the filter
+<a id="header-925ccf"></a>&#x2022; [`remove_accept_encoding_header`](#header-925ccf) - Optional Bool<br>If true, removes accept-encoding from the request headers before dispatching it to the upstream so that responses do not GET compressed before reaching the filter
 
 #### HTTP Proxy More Option Request Cookies To Add
 
@@ -545,47 +545,47 @@ A [`compression_params`](#params-c32856) block (within [`http_proxy.more_option`
 
 A [`site_virtual_sites`](#site-virtual-sites) block supports the following:
 
-<a id="site-virtual-sites-advertise-where"></a>&#x2022; [`advertise_where`](#site-virtual-sites-advertise-where) - Optional Block<br>List of Sites to Advertise. Where should this load balancer be available<br>See [Advertise Where](#site-virtual-sites-advertise-where) below.
+<a id="site-virtual-sites-advertise-where"></a>&#x2022; [`advertise_where`](#site-virtual-sites-advertise-where) - Optional Block<br>Where should this load balancer be available<br>See [Advertise Where](#site-virtual-sites-advertise-where) below.
 
 #### Site Virtual Sites Advertise Where
 
 An [`advertise_where`](#site-virtual-sites-advertise-where) block (within [`site_virtual_sites`](#site-virtual-sites)) supports the following:
 
-<a id="site-virtual-sites-advertise-where-port"></a>&#x2022; [`port`](#site-virtual-sites-advertise-where-port) - Optional Number<br>TCP Listen Port. TCP port to Listen
+<a id="site-virtual-sites-advertise-where-port"></a>&#x2022; [`port`](#site-virtual-sites-advertise-where-port) - Optional Number<br>TCP port to Listen
 
-<a id="site-virtual-sites-advertise-where-site"></a>&#x2022; [`site`](#site-virtual-sites-advertise-where-site) - Optional Block<br>Site. This defines a reference to a CE site along with network type and an optional IP address where a load balancer could be advertised<br>See [Site](#site-virtual-sites-advertise-where-site) below.
+<a id="site-virtual-sites-advertise-where-site"></a>&#x2022; [`site`](#site-virtual-sites-advertise-where-site) - Optional Block<br>Defines a reference to a CE site along with network type and an optional IP address where a load balancer could be advertised<br>See [Site](#site-virtual-sites-advertise-where-site) below.
 
-<a id="port-7cb8fb"></a>&#x2022; [`use_default_port`](#port-7cb8fb) - Optional Block<br>Enable this option
+<a id="port-7cb8fb"></a>&#x2022; [`use_default_port`](#port-7cb8fb) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="site-7107b1"></a>&#x2022; [`virtual_site`](#site-7107b1) - Optional Block<br>Virtual Site. This defines a reference to a customer site virtual site along with network type where a load balancer could be advertised<br>See [Virtual Site](#site-7107b1) below.
+<a id="site-7107b1"></a>&#x2022; [`virtual_site`](#site-7107b1) - Optional Block<br>Defines a reference to a customer site virtual site along with network type where a load balancer could be advertised<br>See [Virtual Site](#site-7107b1) below.
 
 #### Site Virtual Sites Advertise Where Site
 
 A [`site`](#site-virtual-sites-advertise-where-site) block (within [`site_virtual_sites.advertise_where`](#site-virtual-sites-advertise-where)) supports the following:
 
-<a id="site-ip-4eb476"></a>&#x2022; [`ip`](#site-ip-4eb476) - Optional String<br>IP Address. Use given IP address as VIP on the site
+<a id="site-ip-4eb476"></a>&#x2022; [`ip`](#site-ip-4eb476) - Optional String<br>Use given IP address as VIP on the site
 
-<a id="network-647eba"></a>&#x2022; [`network`](#network-647eba) - Optional String  Defaults to `SITE_NETWORK_INSIDE_AND_OUTSIDE`<br>Possible values are `SITE_NETWORK_INSIDE_AND_OUTSIDE`, `SITE_NETWORK_INSIDE`, `SITE_NETWORK_OUTSIDE`, `SITE_NETWORK_SERVICE`, `SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_IP_FABRIC`<br>[Enum: SITE_NETWORK_INSIDE_AND_OUTSIDE|SITE_NETWORK_INSIDE|SITE_NETWORK_OUTSIDE|SITE_NETWORK_SERVICE|SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_IP_FABRIC] Site Network. This defines network types to be used on site All inside and outside networks. All inside and outside networks with internet VIP support. All inside networks. All outside networks. All outside networks with internet VIP support. VK8s service network. - SITE_NETWORK_IP_FABRIC: VER IP Fabric network for the site This Virtual network type is used for exposing virtual host on IP Fabric network on the VER site or for endpoint in IP Fabric network
+<a id="network-647eba"></a>&#x2022; [`network`](#network-647eba) - Optional String  Defaults to `SITE_NETWORK_INSIDE_AND_OUTSIDE`<br>Possible values are `SITE_NETWORK_INSIDE_AND_OUTSIDE`, `SITE_NETWORK_INSIDE`, `SITE_NETWORK_OUTSIDE`, `SITE_NETWORK_SERVICE`, `SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_IP_FABRIC`<br>[Enum: SITE_NETWORK_INSIDE_AND_OUTSIDE|SITE_NETWORK_INSIDE|SITE_NETWORK_OUTSIDE|SITE_NETWORK_SERVICE|SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_IP_FABRIC] Defines network types to be used on site All inside and outside networks. All inside and outside networks with internet VIP support. All inside networks
 
-<a id="site-91e167"></a>&#x2022; [`site`](#site-91e167) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Site](#site-91e167) below.
+<a id="site-91e167"></a>&#x2022; [`site`](#site-91e167) - Optional Block<br>Type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Site](#site-91e167) below.
 
 #### Site Virtual Sites Advertise Where Site Site
 
 A [`site`](#site-91e167) block (within [`site_virtual_sites.advertise_where.site`](#site-virtual-sites-advertise-where-site)) supports the following:
 
-<a id="name-e8af64"></a>&#x2022; [`name`](#name-e8af64) - Optional String<br>Name. When a configuration object(e.g. Virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. Route's) name
+<a id="name-e8af64"></a>&#x2022; [`name`](#name-e8af64) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. Route's) name
 
-<a id="namespace-81a6ad"></a>&#x2022; [`namespace`](#namespace-81a6ad) - Optional String<br>Namespace. When a configuration object(e.g. Virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. Route's) namespace
+<a id="namespace-81a6ad"></a>&#x2022; [`namespace`](#namespace-81a6ad) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. Route's) namespace
 
-<a id="tenant-d56172"></a>&#x2022; [`tenant`](#tenant-d56172) - Optional String<br>Tenant. When a configuration object(e.g. Virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. Route's) tenant
+<a id="tenant-d56172"></a>&#x2022; [`tenant`](#tenant-d56172) - Optional String<br>When a configuration object(e.g. Virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. Route's) tenant
 
 #### Site Virtual Sites Advertise Where Virtual Site
 
 A [`virtual_site`](#site-7107b1) block (within [`site_virtual_sites.advertise_where`](#site-virtual-sites-advertise-where)) supports the following:
 
-<a id="network-31ecf8"></a>&#x2022; [`network`](#network-31ecf8) - Optional String  Defaults to `SITE_NETWORK_INSIDE_AND_OUTSIDE`<br>Possible values are `SITE_NETWORK_INSIDE_AND_OUTSIDE`, `SITE_NETWORK_INSIDE`, `SITE_NETWORK_OUTSIDE`, `SITE_NETWORK_SERVICE`, `SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_IP_FABRIC`<br>[Enum: SITE_NETWORK_INSIDE_AND_OUTSIDE|SITE_NETWORK_INSIDE|SITE_NETWORK_OUTSIDE|SITE_NETWORK_SERVICE|SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_IP_FABRIC] Site Network. This defines network types to be used on site All inside and outside networks. All inside and outside networks with internet VIP support. All inside networks. All outside networks. All outside networks with internet VIP support. VK8s service network. - SITE_NETWORK_IP_FABRIC: VER IP Fabric network for the site This Virtual network type is used for exposing virtual host on IP Fabric network on the VER site or for endpoint in IP Fabric network
+<a id="network-31ecf8"></a>&#x2022; [`network`](#network-31ecf8) - Optional String  Defaults to `SITE_NETWORK_INSIDE_AND_OUTSIDE`<br>Possible values are `SITE_NETWORK_INSIDE_AND_OUTSIDE`, `SITE_NETWORK_INSIDE`, `SITE_NETWORK_OUTSIDE`, `SITE_NETWORK_SERVICE`, `SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_IP_FABRIC`<br>[Enum: SITE_NETWORK_INSIDE_AND_OUTSIDE|SITE_NETWORK_INSIDE|SITE_NETWORK_OUTSIDE|SITE_NETWORK_SERVICE|SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_IP_FABRIC] Defines network types to be used on site All inside and outside networks. All inside and outside networks with internet VIP support. All inside networks
 
-<a id="site-ba773e"></a>&#x2022; [`virtual_site`](#site-ba773e) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Virtual Site](#site-ba773e) below.
+<a id="site-ba773e"></a>&#x2022; [`virtual_site`](#site-ba773e) - Optional Block<br>Type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Virtual Site](#site-ba773e) below.
 
 #### Site Virtual Sites Advertise Where Virtual Site Virtual Site
 
@@ -609,45 +609,45 @@ A [`tls_intercept`](#tls-intercept) block supports the following:
 
 <a id="tls-intercept-custom-certificate"></a>&#x2022; [`custom_certificate`](#tls-intercept-custom-certificate) - Optional Block<br>TLS Certificate. Handle to fetch certificate and key<br>See [Custom Certificate](#tls-intercept-custom-certificate) below.
 
-<a id="tls-intercept-enable-for-all-domains"></a>&#x2022; [`enable_for_all_domains`](#tls-intercept-enable-for-all-domains) - Optional Block<br>Enable this option
+<a id="tls-intercept-enable-for-all-domains"></a>&#x2022; [`enable_for_all_domains`](#tls-intercept-enable-for-all-domains) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="tls-intercept-policy"></a>&#x2022; [`policy`](#tls-intercept-policy) - Optional Block<br>TLS Interception Policy. Policy to enable or disable TLS interception<br>See [Policy](#tls-intercept-policy) below.
+<a id="tls-intercept-policy"></a>&#x2022; [`policy`](#tls-intercept-policy) - Optional Block<br>Policy to enable or disable TLS interception<br>See [Policy](#tls-intercept-policy) below.
 
-<a id="tls-intercept-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#tls-intercept-trusted-ca-url) - Optional String<br>Custom Root CA Certificate. Custom Root CA Certificate for validating upstream server certificate
+<a id="tls-intercept-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#tls-intercept-trusted-ca-url) - Optional String<br>Custom Root CA Certificate for validating upstream server certificate
 
-<a id="tls-intercept-volterra-certificate"></a>&#x2022; [`volterra_certificate`](#tls-intercept-volterra-certificate) - Optional Block<br>Enable this option
+<a id="tls-intercept-volterra-certificate"></a>&#x2022; [`volterra_certificate`](#tls-intercept-volterra-certificate) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="tls-intercept-volterra-trusted-ca"></a>&#x2022; [`volterra_trusted_ca`](#tls-intercept-volterra-trusted-ca) - Optional Block<br>Enable this option
+<a id="tls-intercept-volterra-trusted-ca"></a>&#x2022; [`volterra_trusted_ca`](#tls-intercept-volterra-trusted-ca) - Optional Block<br>Can be used for messages where no values are needed
 
 #### TLS Intercept Custom Certificate
 
 A [`custom_certificate`](#tls-intercept-custom-certificate) block (within [`tls_intercept`](#tls-intercept)) supports the following:
 
-<a id="url-b70ccd"></a>&#x2022; [`certificate_url`](#url-b70ccd) - Optional String<br>Certificate. TLS certificate. Certificate or certificate chain in PEM format including the PEM headers
+<a id="url-b70ccd"></a>&#x2022; [`certificate_url`](#url-b70ccd) - Optional String<br>TLS certificate. Certificate or certificate chain in PEM format including the PEM headers
 
-<a id="algorithms-04b03c"></a>&#x2022; [`custom_hash_algorithms`](#algorithms-04b03c) - Optional Block<br>Hash Algorithms. Specifies the hash algorithms to be used<br>See [Custom Hash Algorithms](#algorithms-04b03c) below.
+<a id="algorithms-04b03c"></a>&#x2022; [`custom_hash_algorithms`](#algorithms-04b03c) - Optional Block<br>Specifies the hash algorithms to be used<br>See [Custom Hash Algorithms](#algorithms-04b03c) below.
 
 <a id="spec-309e16"></a>&#x2022; [`description_spec`](#spec-309e16) - Optional String<br>Description. Description for the certificate
 
-<a id="stapling-e452bc"></a>&#x2022; [`disable_ocsp_stapling`](#stapling-e452bc) - Optional Block<br>Enable this option
+<a id="stapling-e452bc"></a>&#x2022; [`disable_ocsp_stapling`](#stapling-e452bc) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="key-64ce0d"></a>&#x2022; [`private_key`](#key-64ce0d) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Private Key](#key-64ce0d) below.
+<a id="key-64ce0d"></a>&#x2022; [`private_key`](#key-64ce0d) - Optional Block<br>SecretType is used in an object to indicate a sensitive/confidential field<br>See [Private Key](#key-64ce0d) below.
 
-<a id="defaults-a85c93"></a>&#x2022; [`use_system_defaults`](#defaults-a85c93) - Optional Block<br>Enable this option
+<a id="defaults-a85c93"></a>&#x2022; [`use_system_defaults`](#defaults-a85c93) - Optional Block<br>Can be used for messages where no values are needed
 
 #### TLS Intercept Custom Certificate Custom Hash Algorithms
 
 A [`custom_hash_algorithms`](#algorithms-04b03c) block (within [`tls_intercept.custom_certificate`](#tls-intercept-custom-certificate)) supports the following:
 
-<a id="algorithms-bb1c8a"></a>&#x2022; [`hash_algorithms`](#algorithms-bb1c8a) - Optional List  Defaults to `INVALID_HASH_ALGORITHM`<br>Possible values are `INVALID_HASH_ALGORITHM`, `SHA256`, `SHA1`<br>[Enum: INVALID_HASH_ALGORITHM|SHA256|SHA1] Hash Algorithms. Ordered list of hash algorithms to be used
+<a id="algorithms-bb1c8a"></a>&#x2022; [`hash_algorithms`](#algorithms-bb1c8a) - Optional List  Defaults to `INVALID_HASH_ALGORITHM`<br>Possible values are `INVALID_HASH_ALGORITHM`, `SHA256`, `SHA1`<br>[Enum: INVALID_HASH_ALGORITHM|SHA256|SHA1] Ordered list of hash algorithms to be used
 
 #### TLS Intercept Custom Certificate Private Key
 
 A [`private_key`](#key-64ce0d) block (within [`tls_intercept.custom_certificate`](#tls-intercept-custom-certificate)) supports the following:
 
-<a id="info-678e4d"></a>&#x2022; [`blindfold_secret_info`](#info-678e4d) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-678e4d) below.
+<a id="info-678e4d"></a>&#x2022; [`blindfold_secret_info`](#info-678e4d) - Optional Block<br>BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-678e4d) below.
 
-<a id="info-cd6226"></a>&#x2022; [`clear_secret_info`](#info-cd6226) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-cd6226) below.
+<a id="info-cd6226"></a>&#x2022; [`clear_secret_info`](#info-cd6226) - Optional Block<br>ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-cd6226) below.
 
 #### TLS Intercept Custom Certificate Private Key Blindfold Secret Info
 
@@ -661,27 +661,27 @@ A [`private_key`](#key-64ce0d) block (within [`tls_intercept.custom_certificate`
 
 A [`policy`](#tls-intercept-policy) block (within [`tls_intercept`](#tls-intercept)) supports the following:
 
-<a id="tls-intercept-policy-interception-rules"></a>&#x2022; [`interception_rules`](#tls-intercept-policy-interception-rules) - Optional Block<br>TLS Interception Rules. List of ordered rules to enable or disable for TLS interception<br>See [Interception Rules](#tls-intercept-policy-interception-rules) below.
+<a id="tls-intercept-policy-interception-rules"></a>&#x2022; [`interception_rules`](#tls-intercept-policy-interception-rules) - Optional Block<br>List of ordered rules to enable or disable for TLS interception<br>See [Interception Rules](#tls-intercept-policy-interception-rules) below.
 
 #### TLS Intercept Policy Interception Rules
 
 An [`interception_rules`](#tls-intercept-policy-interception-rules) block (within [`tls_intercept.policy`](#tls-intercept-policy)) supports the following:
 
-<a id="interception-f6b646"></a>&#x2022; [`disable_interception`](#interception-f6b646) - Optional Block<br>Enable this option
+<a id="interception-f6b646"></a>&#x2022; [`disable_interception`](#interception-f6b646) - Optional Block<br>Can be used for messages where no values are needed
 
 <a id="match-42a3da"></a>&#x2022; [`domain_match`](#match-42a3da) - Optional Block<br>Domains. Domains names<br>See [Domain Match](#match-42a3da) below.
 
-<a id="interception-e82eca"></a>&#x2022; [`enable_interception`](#interception-e82eca) - Optional Block<br>Enable this option
+<a id="interception-e82eca"></a>&#x2022; [`enable_interception`](#interception-e82eca) - Optional Block<br>Can be used for messages where no values are needed
 
 #### TLS Intercept Policy Interception Rules Domain Match
 
 A [`domain_match`](#match-42a3da) block (within [`tls_intercept.policy.interception_rules`](#tls-intercept-policy-interception-rules)) supports the following:
 
-<a id="value-5de498"></a>&#x2022; [`exact_value`](#value-5de498) - Optional String<br>Exact Value. Exact domain name
+<a id="value-5de498"></a>&#x2022; [`exact_value`](#value-5de498) - Optional String<br>Exact domain name
 
-<a id="value-7aa963"></a>&#x2022; [`regex_value`](#value-7aa963) - Optional String<br>Regex Values of Domains. Regular Expression value for the domain name
+<a id="value-7aa963"></a>&#x2022; [`regex_value`](#value-7aa963) - Optional String<br>Regular Expression value for the domain name
 
-<a id="value-5d0d1d"></a>&#x2022; [`suffix_value`](#value-5d0d1d) - Optional String<br>Suffix Value. Suffix of domain name e.g 'xyz.com' will match '*.xyz.com' and 'xyz.com'
+<a id="value-5d0d1d"></a>&#x2022; [`suffix_value`](#value-5d0d1d) - Optional String<br>Suffix of domain name e.g 'xyz.com' will match '*.xyz.com' and 'xyz.com'
 
 ---