Subject: | Don't eat HTTP::Exception in CAP::Dispatch::PSGI |
While I love what CAP::Dispatch::PSGI does, and enjoy seeing that it
uses HTTP::Exception to report errors, its bitten me a few times that
I'm not able to throw HTTP::Exception objects within my CGI::App;
CAP:D:PSGI eats them instead of letting them bubble up. Would be nice
if it just let them flow right through and get sent upstream the same
way that it does for its own exceptions.