Eric S. Johansson wrote:
odd, very odd. why should a 200 status be reported as a 500?
more debugging in a bit.
very weird. Found a bug in my own code which wasn't reporting status
properly which triggered that error handling in Cherokee which created a
bit of a feedback loop running through my CGI program twice before
finally screeching to a halt.
fixed my bug, my error handling works right which doesn't trigger in
Cherokee edge condition. So, I'm moving forward. Sometimes chasing
after certain bugs is just a dead loss.
--- eric
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
