Are you saying you see nothing output in the browser ?
Have you checked the web-server logs for error message ?
You do say " "Premature end of script headers" in he title - that indicates header problem - but your headers appear correct.

There are plenty of pitfalls trying to get your first CGI script to work - you have the right approach by printing headers first - but you need to check - are the scripts getting loaded by the web server ? executable ? cgi framework loaded ?

The answers are in the web server error logs.

UPDATE: - Looks like you are missing the shebang line.

Here is a working script:

#!/usr/bin/perl
print "Content-Type: text/html;\n\n";
print "<h1>Hello, cgi world</h1>";
print "<table>\n";
print qq|<tr><td><b>$_</b> </td><td> $ENV{$_}</td></tr>\n| for sort ke
+ys %ENV;
print "</table>\n";
[download]

welcome back to 2000 :)

While I'd suggest to abandon CGIs and move to PSGI aware technologies, I remember there was a nph directive for CGIs as you can see at cgifaq.2.html#6: did you tried it too?

See also USING-NPH-SCRIPTS

L*

problem is: "run in the browser" is usually "run on server, wrapped in requests and responses from and to the browser", i.e.
1. browser sends request to server
2. server runs script
3. server sends response back
4. Browser renders response
and if it "fails/does not work", you have to find out which of these four steps is at fault, and decompose that further...

Start here, reply if you have problems. If you've rebuilt a server/environment there's likely part of the config which is wrong. Reading the logs and the debugging tips posted previously will most likely track down the problem.

OK root works fine, but what user the script serving the browser runs under? And with what @INC?

I would like to understand what's going wrong with this :)

;) time to get started, the list is not long

Hi

May I suggest you delve into mod_perl?

Once you get the hang of it, you can do anything you want; I skipped the cgi-bin part altogether
To install, it's easier to use the distribution packages (Debian in my case, so : apt install libapache2-request-perl libapache2-mod-perl2 libapache2-mod-apreq2 )

"I've upgraded and a CGI script no longer works" to "you should use mod_perl" is quite the jump.

True. I was fortunate to find it 15 years ago, when the mod_perl list was very active, hence got a lot of guidance, and there are a few gotchas. Now that I'm replying to you, I recall that I did have to study this book before I could be operational.

However I found the effort was worth it because you can do so much with mod_perl (I build web based applications for a living, the hooks to the Apache response phases are awesome); and you get to write perl code, not cgi code. Also, very efficient.
Anyhow, you are right, not for someone who is building a hobby site. But if one wants to make a serious one, it's a great tool.

https://compta.libremen.com

Logiciel libre de comptabilité générale en partie double