Oops - seems I didn't include the group on my reply
FYI
Here is another test I did (simpler)
Apache Config
PerlModule FNBC::test_statusline
PerlWarn On
SetHandler perl-script
PerlResponseHandler FNBC::test_statusline
Two thoughts...
try status 400 (might be special handling for 4xx unknown)
try r->status instead of/in addition to just r->status_line?
The status 400 (with $r->status_line) produces the same result "HTTP/1.1 200
OK" and with ($r->status) is creates a "HTTP/1.1 400 Bad Request" (the
custom string gets lost)
The $r->status with a code of 499 produces a "HTTP/1.1 400 Bad Request"
On Tue, Sep 28, 2010 at 6:31 AM, William A. Rowe J
On 9/28/2010 12:25 AM, Nico Coetzee wrote:
> The status 400 (with $r->status_line) produces the same result "HTTP/1.1 200
> OK" and with
> ($r->status) is creates a "HTTP/1.1 400 Bad Request" (the custom string gets
> lost)
>
> The $r->status with a code of 499 produces a "HTTP/1.1 400 Bad Reque
$r->status("400");
$r->status_line("400 Error Baby");
Produces: "HTTP/1.1 400 Error Baby"
And
$r->status("207");
$r->status_line("207 Multi-Status");
Produces: "HTTP/1.1 207 Multi-Status"
So, I recon I will try this now in the main app.
Thanks :-)
On Tue, Sep 28, 2010 at 8:26 AM, William A
and... it works now !!
On Tue, Sep 28, 2010 at 8:30 AM, Nico Coetzee wrote:
> $r->status("400");
> $r->status_line("400 Error Baby");
>
> Produces: "HTTP/1.1 400 Error Baby"
>
> And
>
> $r->status("207");
> $r->status_line("207 Multi-Status");
>
> Produces: "HTTP/1.1 207 Multi-Status"
>
> So,
On 9/28/2010 1:32 AM, Nico Coetzee wrote:
> and... it works now !!
I'd hit the same bug from CGI some half-decade ago, sorry I didn't
see where the problem was in the first place :(
