however, DONE is special - it indicates that all content has been sent and the request cycle should proceed straight to the logging phase. from a handler perspective, DONE behaves the same as an error code - it terminates the request cycle.
But the book doesn't say that DONE does break the chain, though it does.
an error in a book? I'm shocked. :)
I suspect that 1.0 logic handled DONE automatically - DONE was captured and passed back to Apache, which took appropriate action. and I suspect this is what you found in 2.0, since you test for DONE but didn't handle it explicitly.
It works exactly the same in 2.0 as in 1.0 (using the current cvs ;), the chain is aborted on !(OK || DECLINED). Any return codes are passed further to Apache.
sounds proper to me. nice work. --Geoff
