On 9/27/2010 6:09 AM, Peter Janovsky wrote:
Are you returning the value of 200 within a module you've written? I
encountered a
similar issue within a C module specific to valid requests. It was resolved
by returning
the internal constant OK.
This is a generalized issue of serving
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
$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.
and... it works now !!
On Tue, Sep 28, 2010 at 8:30 AM, Nico Coetzee nicc...@gmail.com 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
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 :(
Hi - don't know if anybody else have come across this.
I have a mod_perl instance that produces output just as it should (checked
in the logs and I even written the output to file just to have an extra
check).
The tcpdump also show everything is ok.
BUT
The content has the following HTML
Are you returning the value of 200 within a module you've written? I
encountered a similar issue within a C module specific to valid requests. It
was resolved by returning the internal constant OK.
On Sep 27, 2010, at 5:27, Nico Coetzee nicc...@gmail.com wrote:
Hi - don't know if anybody
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
Location /test1
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 Jr.
10 matches
Mail list logo
