Secure Mobile Access 100 10.2 Administration Guide

HTTP (Web) and Secure HTTPS (Web)

The SMA appliance provides proxy access to an HTTP or HTTPS server on the internal network, Internet, or any other network segment that can be reached by the appliance. The remote user communicates with the SMA appliance using HTTPS and requests a URL. The URL is then retrieved over HTTP by the SMA appliance. The URL is transformed as needed and returned encrypted to the remote user.

The Secure Mobile Access administrator can configure Web (HTTP) or Secure Web (HTTPS) bookmarks to allow user access to web-based resources and applications such as Microsoft OWA Premium, Windows SharePoint 2007, Novell Groupwise Web Access 7.0, or Domino Web Access 8.0.1, 8.5.1, and 8.5.2 with HTTP(S) reverse proxy support. Reverse-proxy bookmarks also support the HTTP 1.1 protocol and connection persistence.

HTTPS bookmarks on SMA appliances support keys of up to 4096 bits.

HTTP(S) caching is supported on the SMA appliance for use when it is acting as a proxy Web server deployed between a remote user and a local Web server. The proxy can cache HTTP(S) content on the SMA appliance which the internal Web server deems cacheable based on the HTTP(S) protocol specifications. For subsequent requests, the cached content is returned only after ensuring that the user is authenticated with the SMA appliance and is cleared for access by the access policies. However, Secure Mobile Access optimizes traffic to the backend Web server by using TCP connection multiplexing, where a single TCP connection is used for multiple user sessions to the same web server. Caching is predominantly used for static Web content like JavaScript files, style sheets, and images. The proxy can parse HTML/JavaScript/CSS documents of indefinite length. The administrator can enable or disable caching, flush cached content, and set the maximum size for the cache.

Content received by the SMA appliance from the local Web server is compressed using gzip before sending it over the Internet to the remote client. Compressing content sent from the appliance saves bandwidth and results in higher throughput. Furthermore, only compressed content is cached, saving nearly 40-50 percent of the required memory. Note that gzip compression is not available on the local (clear text side) of the SMA appliance, or for HTTPS requests from the remote client.

Was This Article Helpful?

Help us to improve our support portal

Techdocs Article Helpful form

Techdocs Article NOT Helpful form

  • Still can't find what you're looking for? Try our knowledge base or ask our community for more help.