These types of connection issues might be common when enterprises employ custom applications. Though the connection issues are related to the server, administrators might mistakenly conclude that the ProxySG is the source of the problem because of the issues' exception page from the proxy. When the option is enabled, the ProxySG essentially closes connections to clients upon a server connection error or timeout. If users or eval' customers see an exception page instead of the default browser error, they are more likely to think the proxy causes the connection failure even if the web server was at fault.
In SGOS 220.127.116.11 or later this option can only be enabled/disabled through the Command Line Interface (CLI):
To enable: SGOS#(config) http exception-on-network-error
To disable: SGOS#(config) http no exception-on-network-error
To prevent this problem, set to disable:
SGOS#(config) http no exception-on-network-error
see result as:
In this configuration, the proxy will pass the same network breakage from server to client, either a TCP FIN or RESET et c. with the client to handling it as though no proxy were present. The end result is the client (either browser or APPS) will continue to work.
Volume 2: Proxies and Proxy Services
Section C: Managing the HTTP Proxy Performance