in reply to Re: Re: Perl and XML
in thread Perl and XML

No, you need that too, and it must be a proper path to perl too, but that's usually called the shebang line.

No, I'm now talking about CGI 101, you can use a simple 

print "Content-type: text/plain\n\n";

[download]
before your print anything else, or something similar but more advanced from one of the CGI modules.

For simple experimentation, it'd be best to use something like 

use CGI::Carp 'fatalsToBrowser';

[download]
because then you'll get your Perl error messages in the browser window, too.

Replies are listed 'Best First'.
Re: Re: Re: Re: Perl and XML
by BzBeauty (Sexton) on Mar 16, 2004 at 23:30 UTC
    thank you. that fixed it. maybe I should rename myself to CGI<101 so yeah, how do you use the 
    use CGI::Carp 'fatalsToBrowser';

    [download]
    do you need the 
    print "Content-type: text/plain\n\n";

    [download]
    for that to work as well. Cause I stuck the fatalsToBrowser in their first hoping for a decent error message - but no same error. And of course, when I put the header in their, it works, so no error at all.
[reply]
[d/l]
[select]
      "fatalsToBrowser" will only kick in in case Perl produces an error. In this case, it didn't, forgetting the header and closing off the headers, was completely your own mistake. Perl itself didn't complain, but still, the webserver wasn't happy.
[reply]

In Section Seekers of Perl Wisdom