I need a little help on setting up Active Perl on Win XP Pro's II5.

I have active Perl installed an working from the command line in c:\perl\bin

When I type localhost\anything.cgi in the browser I can't run cgi.... asp works fine of course.

Is there a setting or somthing I need to look at?


http://www.iuni.com/...tware/web/index.html
Links Plugins

You should be using a forward slash...anyway what is the error?

http://localhost/install.cgi gives:

No web site is configured at this address.

install.cgi is the Links SQL install file, but I have tried some really simple cgi files also, which return the same error.


http://www.iuni.com/...tware/web/index.html
Links Plugins

Try 127.0.0.1 ...what is your machines ip?

24.67.207.28

127.0.0.1 returned the same error


http://www.iuni.com/...tware/web/index.html
Links Plugins

http://24.67.207.28/install.cgi

%1 is not a valid Win32 application.


http://www.iuni.com/...tware/web/index.html
Links Plugins

Could you not use Apache...it would save you lots of headaches?

http://www.gossamer-threads.com/...application_P126563/

I guess I could use Apache


http://www.iuni.com/...tware/web/index.html
Links Plugins

Yeah, thanks.

I seems to be just the cgi extenstion, .pl works fine.

I'll check around google...


http://www.iuni.com/...tware/web/index.html
Links Plugins

I got apache working


http://www.iuni.com/...tware/web/index.html
Links Plugins

Yay :)

I don't know why ActivePerl doesn't make .cgi associated with Perl by default, since everybody uses .cgi. Anyway, just right-click on any .cgi file, choose open with, and browse to perl (usually at C:/Perl/bin/perl.exe). choose to always use the program to open the type of file. You should then be able to use .cgi scripts as you do .pl scripts.

--Philip
Links 2.0 moderator

Thanks Philip... I finally worked it out after playing around with it for a few hours.

I have since installed Apache also, and now users can't access my machine remotely. (They could under IIS).

Oh well, fixed one thing, broke another


http://www.iuni.com/...tware/web/index.html
Links Plugins

>>>
I don't know why ActivePerl doesn't make .cgi associated with Perl by default, since everybody uses .cgi. Anyway, just right-click on any .cgi file, choose open with, and browse to perl (usually at C:/Perl/bin/perl.exe). choose to always use the program to open the type of file. You should then be able to use .cgi scripts as you do .pl scripts.
<<<

Eh?.....its apache you setup to associate with cgi files....activeperl associates with perl but you dont want to choose to open pl scripts with perl.exe otherwise it gives them all a nasty yellow icon and its annoying trying to view the code as you have to right click otherwise it tries to execute the code in the command prompt window.

I think I misread part of the post. No one uses .pl for executable scripts anyway, do they? I never have. I've always thought of "pl" meaning "perl library", an included or required subset of funtions. The yello icon is kind of gross, isn't it?

who cares anyway?

--Philip
Links 2.0 moderator

Yeah i've never really understood the difference between .pl and .cgi ....GT use incoming.pl for GossamerMail....wonder why not .cgi like the rest.

I always though it was because .pl's are run from a command line or from cron like a regular perl script and .cgi are used for web. That was just a big assumption on my part though. They can both be executed in either scenario :/

~Charlie

[edit]bug => big[\edit]

http://developer.irt.org/script/5600.htm

http://developer.irt.org/script/5601.htm

Ooops, I guess I wasn't very clear in my explanation. I know what cgi is and just about any language can be used to write them. I was speaking more from a nomenclature standpoint. i.e. perl scripts with a .pl would be used as a, well, perl script and perl scripts with a .cgi would be used specifically for web apps. Isn't .pl the standard file extension for a perl script when you are making a unix utility? Like I mentioned, it was just an assumption on my part.

~Charlie

I guess really then .cgi's should be for any script accessible through a browser and .pl should be for system scripts like cronjobs etc, although I do see people making .pl files web accessible...hmm may thats just people like Matt Wright

Ugg, I do that from time to time. I guess you need to start somewhere :)

~Charlie

Well it doesn't really matter I suppose, but I just feel better psychologically using .cgi (don't ask me why...but I think it stems back to when I first started learning perl and now I associate .pl with Internal Server Error )

I use .pl for Perl programs. I use .cgi for CGI programs.

If I have a complex script, maybe only 1 file will be named with a .CGI extension as that will be the only script interfacing through CGI with a web browser. All the rest will carry out Perl functions but never actually interfacing through CGI directly.

- wil

I never use .pl files. For example my helpdesk script uses about 6 cgi scripts and about 50 .pm's