Would folks like to beta test CGI.pm version 2.57?  "make test" will
fail with two html-related errors, but these are just related to
change in the HTML 4.0 DTD and nothing to worry about.

Lincoln

CGI.pm-2.57.tar.gz




Brian Reichert writes:
 > Sorry about the confusing subject line.
 > 
 > I'm witnessing a symptom:
 > 
 > Using apache_1.3.9 and mod_perl-1.21 and CGI.pm-2.56 under 3.2-STABLE.
 > 
 > I'm writing a cookie-based access handler.  (Based very directly
 > on the Apache::TicketMaster example in the Eagle book.)
 > 
 > My perl handler uses:
 > 
 >   use CGI qw(:standard);
 > 
 > then eventually calls
 > 
 >   header()
 > 
 > Deep down, my error log says
 > 
 >   [Fri Jan 28 17:59:24 2000] [error] Can't call method "send_cgi_header" on
 >   an undefined value at (eval 11) line 50.
 > 
 > Much digging shows that at around line 1278:
 > 
 >     my $header = join($CRLF,@header)."${CRLF}${CRLF}";
 >     if ($MOD_PERL and not $nph) {
 >         my $r = Apache->request; 
 >         $r->send_cgi_header($header);  
 >         return ''; 
 >     }
 >     return $header;
 > 
 > the call to Apache->request returns an undef.
 > 
 > The pod for Apache asserts:
 > 
 >        Apache->request([$r])
 > 
 >            The Apache->request method will return a reference to
 >            the request object.
 > 
 > but fails to disclose under what cirumstances the call fails.  I
 > most certainly have an Apache request object at my disposal, my
 > handler otherwise copes with it.
 > 
 > Does anyone have any opinions or pointers?
 > 
 > Thanks...
 > 
 > -- 
 > Brian 'you Bastard' Reichert         [EMAIL PROTECTED]
 > 37 Crystal Ave. #303                 Daytime number: (781) 899-7484 x704
 > Derry NH 03038-1713 USA                      Intel architecture: the left-hand path

-- 
========================================================================
Lincoln D. Stein                           Cold Spring Harbor Laboratory
[EMAIL PROTECTED]                                   Cold Spring Harbor, NY
========================================================================

Reply via email to