Re: Fwd: All responses are 200 (server error)

2010-09-27 Thread William A. Rowe Jr. 
Two thoughts...

try status 400 (might be special handling for 4xx unknown)

try r->status instead of/in addition to just r->status_line?

Re: Fwd: All responses are 200 (server error)

2010-09-27 Thread Nico Coetzee 
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 Jr. wrote:

> Two thoughts...
>
> try status 400 (might be special handling for 4xx unknown)
>
> try r->status instead of/in addition to just r->status_line?
>

Re: Fwd: All responses are 200 (server error)

2010-09-27 Thread William A. Rowe Jr. 
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 Request"

Sort of confirms my theory.

Set status to 400 and set status_line to 400 Custom Message, see what happens?

I suspect that 499 simply isn't allowed, which is wrong, but the current
behavior none the less.

Re: Fwd: All responses are 200 (server error)

2010-09-27 Thread Nico Coetzee 
$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. Rowe Jr. wrote:

> 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 Request"
>
> Sort of confirms my theory.
>
> Set status to 400 and set status_line to 400 Custom Message, see what
> happens?
>
> I suspect that 499 simply isn't allowed, which is wrong, but the current
> behavior none the less.
>

Re: Fwd: All responses are 200 (server error)

2010-09-27 Thread Nico Coetzee 
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, I recon I will try this now in the main app.
>
> Thanks :-)
>
>
>
> On Tue, Sep 28, 2010 at 8:26 AM, William A. Rowe Jr. 
> wrote:
>
>> 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 Request"
>>
>> Sort of confirms my theory.
>>
>> Set status to 400 and set status_line to 400 Custom Message, see what
>> happens?
>>
>> I suspect that 499 simply isn't allowed, which is wrong, but the current
>> behavior none the less.
>>
>
>

Re: Fwd: All responses are 200 (server error)

2010-09-27 Thread William A. Rowe Jr. 
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 :(