in reply to for mod-perl gurus

It's difficult to figure out what to tell you based on this problem description, but it sounds like you were running your scripts under CGI rather than mod_perl, and maybe still are. Did you add anything to your httpd.conf about using Apache::Registry? Can you post the snippet of your conf file that deals with mod_perl?

The problem with the bad query results sounds like a bug in your perl code, and you should follow normal debugging procedures to figure out what's wrong. If you really are running under mod_perl, this may be an issue with global variables being saved between invocations of the script.

Replies are listed 'Best First'.
Re: Re: for mod-perl gurus
by ralphie (Friar) on Nov 20, 2001 at 02:16 UTC
    actually, i can determine the validity of the result sets in pretty straightforward fashion, and i'm getting the right stuff ...

    chunks of httpd.conf

    <Directory /home/username/mod-perl/>
    AllowOverride None
    Options ExecCGI
    Order allow,deny
    Allow from all
</Directory>

<IfModule mod_perl.c>
    Alias /mod-perl /home/username/mod-perl
   <Location /mod-perl>
  SetHandler perl-script
    PerlHandler Apache::Registry
    Options +ExecCGI
    </Location>
</IfModule>

 Alias /perl/  /home/username/mod-perl/

    [download]
[reply]
[d/l]
      Okay, it looks like if you request a URL in /mod-perl you will be running correctly uder Registry. You can test this by printing out the special $ENV{MOD_PERL} variable in your script. Before you installed this, I assume you were running under CGI, which yuo configured with the ExecCGI option.

      If you're getting the right data back in your script, but it isn't going to the screen, you may be using globals incorrectly (they don't get cleared out between requests under Apache::Registry). If you're using modules and changing them without restarting the server, your changes may not be getting picked up. But I thought you said you were NOT getting the right stuff?

[reply]

In Section Seekers of Perl Wisdom