Re^3: Perl Mason & Apache: getting Apache2::Const to work

It is 404 now, but that's subject to change at any time in any future apache release, so don't hardcode 404.

I think you need to add this before using the constant:

use Apache2::Const -compile => qw(NOT_FOUND);
[download]

Comment on Re^3: Perl Mason & Apache: getting Apache2::Const to work Download Code

Replies are listed 'Best First'.
Re^4: Perl Mason & Apache: getting Apache2::Const to work by jfroebe (Parson) on Sep 12, 2006 at 13:45 UTC
Actually, Apache has nothing to do what the error codes are but I get your point :) Jason L. Froebe Team Sybase member No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1	[reply]
Re^5: Perl Mason & Apache: getting Apache2::Const to work by perrin (Chancellor) on Sep 12, 2006 at 15:07 UTC
No, you're misunderstanding. The return here is NOT an HTTP status code. It is an internal apache thing. It happens to be 404, but that's just a convenient number the apache devs chose. The HTTP status code is something you set with $r->status, not the return from the sub, and it is Apache::Const::HTTP_NOT_FOUND (which is 404 and you really could just use the number), rather than the one you're using here.	[reply]