We've just upgraded a SunOS machine from Apache 1.3.9 + mod_perl 1.21
(dynamically linked) to Apache 1.3.19 + mod_perl 1.25 (statically
linked). I have a CGI/Perl script, handled as normal by perl-script
and Apache::Registry. Now, this CGI script sometimes returns a page
with status something like '403 Forbidden', including full content and
full headers. With the old version, the perl_handler function
returned with status=0 (OK), even if the HTTP status was going to be
403, and then Apache was quite happy with this. However, in the
current combination, the perl_handler function returns with the HTTP
status, so that the Apache core adds on its own content.
I am not sure what interactions are going on here, as at first sight,
this doesn't appear to happen with Linux running the same combination
(dynamically linked, though).
Any ideas, anyone?
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London
Debian GNU/Linux Developer, see http://people.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
