Hi All,
I'm testing an application that uses persistent HTTP connections over a Gauntlet 6.0 firewall on Solaris. One of the connection types uses HTTP 1.0 with the Keep-Alive connection token in the header. The other one uses HTTP 1.0 and specifies a content length of 2GB in the header to keep the POST connection alive. When I try to pass either of these through Gauntlet it resets the connection. Does anyone know of any config settings in Gauntlet that can be tweaked to allow persistent connections? Thanks, Tim Swift Senior QA Engineer Groove Networks, Inc. [EMAIL PROTECTED] -- Firewalls mailing list - [ [EMAIL PROTECTED] ] To unsubscribe: http://www.isc.org/services/public/lists/firewalls.html
