THANK YOU MICHAEL!
I was beating my head against the wall. I even created a stripped
down module that had nothing but one run-mode, and no init, setup,
teardown or any other includes, and I was STILL getting the error.
I owe you a beer or six.
Joel
On 8/13/06, Michael Petnuch <michael@xxxxxxxxxxx> wrote:
Joel:
I guess I am no longer the only one experiening this problem. See
this thread (http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
msg05428.html). As for a solution, I edited the Dispatch module
(around line 608) to look like this:
unless($r->status == 200) {
return $r->status;
} else {
return OK();
}
Michael
On Aug 13, 2006, at 4:44 PM, Joel Gwynn wrote:
> On 8/9/06, Joel Gwynn <joelman@xxxxxxxxx> wrote:
>> So in my bumbling through setting up CA::Dispatch w/mod_perl, I'm
>> getting this weird behavior where my page renders, but at the end is
>> tacked on an Apache 200 OK response, followed by:
>>
>> "OK
>>
>> The server encountered an internal error or misconfiguration and was
>> unable to complete your request."
>>
>> What's up with this? Have I lost control of my Bucket Brigades, like
>> the wizard's brooms?
>>
>
> When I telnet on port 80, it appears that Apache is sending back the
> HTML content, and THEN the "200 OK" header with the error message.
> I've confirmed that this doesn't happen when using normal mod_perl,
> only using CGI::Application::Dispatch.
>
> Any ideas?
>
> ---------------------------------------------------------------------
> Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
> http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
> To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
> For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
>
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
