> It seemed that early in mod_perl use,
> the return codes would be the literal status codes, like 500 for
> server error, 302 for redirect and 200 for success. This is
> then very different in mod_perl 2, and hopefully I can implement
> this is some rational way so that Apache::ASP can still do s
> although nothing is reported in the error log, and the
> status in the access log is reported as 200. The problem
> arises from returning '200' from Apache::Hello; changing
>return 200;
> to
>return Apache::OK;
> fixes things.
>
> Is there something wrong in principle with returning an
>
I've documented the mod_perl 2.0 handler return value "protocol" here:
http://perl.apache.org/docs/2.0/user/handlers/intro.html#Handler_Return_Values
Please read and submit patches if something is wrong/unclear. Muchas Gracias.
__
Stas
Geoffrey Young wrote:
And if you return Apache::HTTP_OK, in response handler it's
essentially an error too. If people feel really strong about it, we
can put back the special case for Apache::HTTP_OK. Though if you think
about it, it makes your life much simpler is you remember that all you
h
Geoffrey Young <[EMAIL PROTECTED]> writes:
> for the record, this is exactly how apache behaves for people writing
> C modules
> - it expects a handler to return OK, DECLINED, DONE, or
> _some_http_status_all_of_which_mean_"error"
>
> so, I'd rather not go back to 200 == OK. not only does this
And if you return Apache::HTTP_OK, in response handler it's essentially
an error too. If people feel really strong about it, we can put back the
special case for Apache::HTTP_OK. Though if you think about it, it makes
your life much simpler is you remember that all you have to return in OK
or
Hi Stas,
On Sat, 22 Nov 2003, Stas Bekman wrote:
> [snip]
> so only when a handler returns OK or DECLINED will the request loop continue
> [snip]
> if you think about it, it makes your life much simpler is you remember
> that all you have to return in OK or DECLINED to continue and anything
> el
Perrin Harkins wrote:
On Sat, 2003-11-22 at 11:55, Randy Kobes wrote:
Is there something wrong in principle with returning an
explicit status of, eg, 200, rather than using the Apache::*
constants?
As I understand it, they are two different things. The Apache constants
are for telling apache wh
On Sat, 2003-11-22 at 11:55, Randy Kobes wrote:
> Is there something wrong in principle with returning an
> explicit status of, eg, 200, rather than using the Apache::*
> constants?
As I understand it, they are two different things. The Apache constants
are for telling apache what's going on and
I've noticed the following with the current cvs build of
mod_perl 2, under Win32 ActivePerl 807 and Apache/2.0.48,
and was wondering if I'm not understanding something. I
first noticed it with Apache::ASP, but the following handler
also illustrates it:
==
10 matches
Mail list logo
