Application-protected web resources

Protected web resources are available in Access Gateway version 2022.1.1 and later to support Access Gateway load balancing.

The Protected Web Resource page includes information on load balancing or back end protected web resources, load balancing health checks, host headers, and so on. It includes the following:

Field	Description	Default
Load Balancing by Access Gateway	Enables or disables load balancing. When enabled, URL scheme, and configured protected web resources, can be entered, as well as other options.	Disabled
Load Balancer Health Check	Enables or disables load balancing health checks. Use the Edit button to configure load balancer health checks.	Disabled
URL scheme	The URL scheme or protocol used to access back end protected resources. Supported schemes are HTTP and HTTPS.	HTTP
Host Header Host Header Value	Represents the value of the host header passed to the back end protected web resources. When enabled, the external fully qualified external name is used (for example, noauth.atko.com). When disabled, a custom value may be entered.	Disabled application specific
Load Balancing Cookie	Cookie value associated with each request sent to back end protected web resources.	Generate value
Configured Protected Web Resources	A set of back end protected web resources including weights. Prefixed by URL scheme. See Add Protected Web Resource.	N/A

Add Protected Web Resource

Click Add Protected Web Resource to add a protected web resource.

Field	Description
Hostname	Fully qualified host name of the protected web resource. Must be resolvable in DNS.
Weight	Associated weight. Value from 0-100. 0 (zero) is a special value that means a host is not in use. Three protected web resources, where each has a weight of 1, will be routed an equal numbers of requests. Two protected web resources, that have weights 1 and 2, have twice as many requests (or 66% of the total number of requests) routed to the hostname with a weight of 2, compared to the hostname with a weight of 1.

Health checks

Health checks are used to determine if a back end protected web resource can service requests.

Field	Value	Default
Path	URI to resource used in health check.	/
Method	HTTP method used.	Always GET
Status code	HTTP status code used to determine health.	200
Interval	Interval between health checks in seconds.	10
Request timeout	Health check request timeout in seconds.	1
Healthy threshold	Number of successful requests before a host is considered healthy.	3
Unhealthy threshold	Number of failed requests before a host is considered unhealthy.	3

Protected web resources can be in one of three states:

State	Icon	Description
Active		Initial state, host entered and active but health unknown. When health checks are disabled, protected web resources never leave this state.
Healthy		Host is responding based on health check settings.
Unhealthy		Host isn't responding; new requests won't be routed to it.

Related topics

Load balancing

Load balancing health checks

Add Access Gateway load balancing to an existing application