On Dec 13, 2005, at 7:32 PM, Ruediger Pluem wrote:
On 12/14/2005 12:59 AM, Jim Jagielski wrote:
On Dec 13, 2005, at 1:28 PM, Ruediger Pluem wrote:
[..cut..]
The reason the other patch didn't do this is that,
upon reflection, closing the client connection at
this point does not seem quite right. Closing
it simply because the gateway died just doesn't
feel right, and seems almost overkill. I think
simply setting the error bucket to allow the rest
of the chain to correctly handle it, is the best
we could (and should) do :/
Sorry, but I think I have to disagree.
There is nothing that can be handled anymore since the headers had
been sent to the client.
The only part of the chain that handles error buckets so far is the
http header filter which is gone at
this point of time.
IMO, that's the problem... The core output filter should be aware of
this error. Not sure if "magically" noticing this when
removing empty buckets is the right solution...
