Received: (qmail 35640 invoked by uid 501); 26 Sep 2000 11:22:22 -0000
Message-Id: <20000926112222.35634.qmail@locus.apache.org>
Date: 26 Sep 2000 11:22:22 -0000
From: Ulf Bahrenfuss <ulf.bahrenfuss@uni-vechta.de>
Reply-To: ulf.bahrenfuss@uni-vechta.de
To: submit@bugz.apache.org
Subject: Proxy continues connection to Push-Server, though Client has gone.
X-Send-Pr-Version: 3.110

>Number:         6585
>Category:       mod_proxy
>Synopsis:       Fix from PR 8090 applied
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Sep 26 04:30:01 PDT 2000
>Closed-Date:    Mon Sep 24 13:24:11 PDT 2001
>Last-Modified:  Mon Sep 24 13:24:11 PDT 2001
>Originator:     ulf.bahrenfuss@uni-vechta.de
>Release:        1.3.9
>Organization:
>Environment:
Linux 2.2.10 #7 Suse 6.2
egcs-2.91.66 (1.1.2 release)

>Description:
While accessing a Webcam with Server-Push technology (like an Axis cam) the
Proxy continues to get traffic from the Cam after the Client that requested the
page has gone away. This results in a heavy traffic load. Cache Force Completion
is deaktivated (100).
This seems like a reproducable variant of my report #5391
>How-To-Repeat:
Try to access 194.94.26.168 and then Server Push from the Cam via the 
Apache-Proxy. After starting the Push the Proxy won't terminate even after the
Client exited and even the Client computer is down.
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: chuck
State-Changed-When: Mon Sep 24 13:24:11 PDT 2001
State-Changed-Why:
Fix from PR 8090 applied
Synopsis-Changed-From: Proxy continues connection to Push-Server, though Client has gone.
Synopsis-Changed-To: Fix from PR 8090 applied
Synopsis-Changed-By: chuck
Synopsis-Changed-When: Mon Sep 24 13:24:11 PDT 2001
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]