On Fri, Jul 06, 2001 at 01:50:57PM -0700, Doug MacEachern wrote:
> On Wed, 23 May 2001, Julian Gilbey wrote:
>
> > On Mon, May 21, 2001 at 06:36:54PM +0100, Julian Gilbey wrote:
> > > 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.
>
> can you post an example script? i think the current sources do the right
> thing. re-reading your message, it sounds like you should be using a
> CustomResponse (or $r->custom_response) if you want to generate a 403
> response yourself. i realize what you're doing 'worked' in older
> mod_perls, but that was a bug, not a feature.
I'm using CGI.pm, version 2.56, with the
print header(-status => '403 Forbidden');
function. So perhaps it's a CGI.pm bug?
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/
