Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All
     

    Related Documentation

     

    Proxy/Backends

    The Proxy/Backends window let you customize how to handle proxying content to and from WebApp Secure. Request and response timeouts, listening ports, and compression settings can be set here in addition to other settings.

    Configure or use the defaults for the following fields:

    • Load Balancer Method–When using WebApp Secure as a load balancer for multiple application servers, this setting defines how the appliance segregates traffic. The pulldown list offers these selections:
      • Round Robin (default)–Attempt to contact all servers in a rotational fashion.
      • Sticky–Act 'Fair' for the first request of each incoming session, but route to the same server for each subsequent request using that session.
      • IP Hash–Act 'Fair' for the first request of each incoming IP, but route to the same server for each subsequent request using the same IP.
    • HTTP Server Port–The port would you like exposed for incoming HTTP connections. It is recommended to leave this as the default :80
    • Max Request Size–The maximum total size (in MB) for a request that will be allowed through WebApp Secure to the backend.
    • Request Timeout–The timeout limit for client requests. Any request taking longer than this to transfer data to the server is terminated.
    • Response Timeout–The timeout limit for server responses. Any response that takes longer than this timeout to transfer data to the client is terminated.
    • Connection Timeout–The maximum time WebApp Secure will wait to get a connection from the backend server(s).
    • HTTP Compression Enabled–True or False–Whether or not to compress (using gzip) responses as they pass through WebApp Secure
    • HTTP Version–1.0 or 1.1. Choose an HTTP version for proxied traffic.

    Health Check–Use the fields here to override existing health check settings.

    Test Health Check Settings–Click here to test health check configuration settings.

    • Enabled–True or False–Whether or not to enable the Health Check function.
    • HTTPS Enabled–True or False–Whether or not health checks should be performed over HTTPS.

      Note: The health checks will still be performed over plain HTTP.

    • Delay–The time WebApp Secure should wait between Health Checks.
    • Fail Count–How many health checks fail before the server is marked as unavailable.
    • Timeout– How long for WebApp Secure to wait for a response from the server while issuing a health check.

    Servers–see Application Backend Overrides.

     

    Related Documentation

     

    Published: 2015-02-04