SRA Overview | 33Network Resources OverviewNetwork Resources are the granular components of a trusted network that can be accessedusing the SRA appliance. Network Resources can be pre-defined by the administrator andassigned to users or groups as bookmarks, or users can define and bookmark their ownNetwork Resources.The following sections describe types of network resources supported by the SRA appliance:• “HTTP (Web) and Secure HTTPS (Web)” section on page 33• “Telnet (Java)” section on page 34• “SSHv1 and SSHv2 (Java)” section on page 34• “FTP (Web)” section on page 34• “File Shares (CIFS)” section on page 34• “Remote Desktop Protocols and Virtual Network Computing” section on page 34• “Application Protocols Using RDP” section on page 35• “Microsoft Outlook Web Access” section on page 36• “Windows Sharepoint Services” section on page 37• “Lotus Domino Web Access” section on page 38• “Citrix Portal” section on page 38HTTP (Web) and Secure HTTPS (Web)The SRA appliance provides proxy access to an HTTP or HTTPS server on the internalnetwork, Internet, or any other network segment that can be reached by the appliance. Theremote user communicates with the SRA appliance using HTTPS and requests a URL. TheURL is then retrieved over HTTP by the SRA appliance. The URL is transformed as needed,and returned encrypted to the remote user.The SRA administrator can configure Web (HTTP) or Secure Web (HTTPS) bookmarks to allowuser 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 supportthe HTTP 1.1 protocol and connection persistence.HTTPS bookmarks on SRA 4600/4200 appliances support keys of up to 2048 bits.HTTP(S) caching is supported on the SRA appliance for use when it is acting as a proxy Webserver deployed between a remote user and a local Web server. The proxy is allowed to cacheHTTP(S) content on the SRA appliance which the internal Web server deems cacheable basedon the HTTP(S) protocol specifications. For subsequent requests, the cached content isreturned only after ensuring that the user is authenticated with the SRA appliance and iscleared for access by the access policies. However, SRA optimizes traffic to the backend Webserver by using TCP connection multiplexing, where a single TCP connection is used formultiple user sessions to the same web server. Caching is predominantly used for static Webcontent 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, flushcached content and set the maximum size for the cache.Content received by the SRA appliance from the local Web server is compressed using gzipbefore sending it over the Internet to the remote client. Compressing content sent from theappliance saves bandwidth and results in higher throughput. Furthermore, only compressedcontent is cached, saving nearly 40-50% of the required memory. Note that gzip compressionis not available on the local (clear text side) of the SRA appliance, or for HTTPS requests fromthe remote client.
