🚀 go-pugleaf

Pak Chan <Pak.Chan@metameme.demon.co.uk> wrote in message
news:MPG.13dcd9ad722cdebc989689@news.demon.co.uk...
> In article <x7vgy8fd3v.fsf@indy1.watching.org>, jrg@blodwen.demon.co.uk
> says...
> > Pak Chan <Pak.Chan@metameme.demon.co.uk> writes:
> > > I've contacted Demon commercial tech support, but they have absolutely
no
> > > idea (clue?) as to why it fails to work. The only thing that they can
> > > think of is that I'm loading the CGI library module in my scripts
> > > (perfectly understandable, given that they are CGI scripts!). They
have
> >
> > 'Internal server' errors generally mean that something is being output
> > at an inappropriate moment - mixing up errors with where the HTTP
> > headers are supposed to be.
> >
> > You could try, before any of the 'use' statements, something like
> >
> > BEGIN {
> > $| = 1;
> > print "Content-Type: text/plain\r\n\r\n";
> > }
> >
> > in an effort to print a valid content-type header before anything else
> > fails to initialise correctly and prints out error messages.
> >
> > Or, look for information on the 'xx-' debugging feature on Demon's
> > servers.  (I don't know if it's mentioned in the documentation -
> > anyone?)
>
> Thanks. I've just tried the xx- feature, and it's quite illuminating:
>
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 22,
> next 2 tokens "use CGI"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 30,
> next 2 tokens "new CGI"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 34,
> next 2 tokens "->"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 36,
> next 2 tokens "->"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 38,
> next 2 tokens "->"
> parse error in file /www/cgi-bin/www.lawsoncars.com/xx-sm.pl at line 54,
> next 2 tokens "->"
> Execution of /www/cgi-bin/www.lawsoncars.com/xx-sm.pl aborted due to
compilation errors.
>
> I was given the impression that Demon ran Perl 5 on their servers. Is
> this not the case? Anyone from Demon Internet care to confirm this?
>

I'm not sure the CGI package is part of the standard perl distribution.
But the error doesn't look like a missing package - normally it says "cant
locate XXX.pm at script line yy".
Maybe you need to be explicit about perl5.

Paul