On Dec 30, 2007 3:45 PM, Kate Yoak [EMAIL PROTECTED] wrote:
returning 200 as a scalar from a content handler causes Apache to
spit up Internal Server Error html despite a '200 OK' status.
There is no error or warning in the log, nor any other indication of
a problem
This is more of an apache
I have solved the problem. I was returning 200 instead of using
Apache2::Const::OK. My response was indeed interpreted as 'OK by
apache - but not by some place somewhere else. There was no error
message anywhere. I'll modify the bugreport below to have it
addressed or not at the
I am using mp2bug format for the message. Hope, that's ok!
=
-8-- Start Bug Report 8--
1. Problem Description:
I have just upgraded to apache2/modperl2 (bug report with specific
version info is below) and I am getting the
