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. So the client will be most likely waiting for more data on this connection if the content-length was bigger than what was sent so far. So from my point of view closing the connection is the only possibility to signal the client that something got irrevocably wrong. Regards Rüdiger
