On Dec 8, 2005, at 8:31 AM, Brian Akins wrote:
Graham Leggett wrote:
At this point the frontend connection has already sent a 200 Ok,
it's already sent headers like Content-Length, etc, at this point
there is no graceful way of handling the error or sending "bad
gateway".
I agree. There is no way we can inform the client of the problem.
Currently,
- we just cease sending the client data.
- The client is rather confused
- other modules think the request completed successfully.
If we c->aborted:
- we just cease sending the client data.
- we close connection to client
- The client is rather confused
- other modules know that the request was aborted and can react
So, currently, we would have to change multiple modules to notice
some other error notification. Meanwhile, the client gains
nothing. So, I say, just use c->aborted
+1
