in reply to PerlScript on IIS

I'm afraid theAcolyte 's reply is plain wrong.

Update: Based on theAcolyte 's reply to my post, I revoke this statement, and offer apologies. If the OP had asked about Client-side scripting (Why would he want to do that in perl?), his reply is valid.

The .asp files need to be server by a WEB SERVER, such as IIS.

The client browser is irrelevent. What the web server does is convert/run the asp code (regardless of whether it is Javascript, VB or perl), and send HTML to the browser.

What you need to do is to place the asp code on a web server (which could be your own machine), and view it using a URL pointing to that page within the server.

Your URL should NOT be something like C:\pathname\file.asp - that will be served by the file system, not by the web server.

Your URL should be http://Servername/pathname/file.asp

    Earth first! (We'll rob the other planets later)

Replies are listed 'Best First'.
Re^2: PerlScript on IIS
by theAcolyte (Pilgrim) on Jul 19, 2004 at 04:34 UTC
    Um ... no, its not wrong (my answer). The orignal question said:
    My .asp files containing perlscript don't run in either IE or Netscape.

    So I'm assuming the poster means Client-Side perlscript (to be executed in the browser) ... and to quote from the activestate documents:

    Client-Side PerlScript has Perl embedded within your HTML documents. All PerlScript code must be contained within <SCRIPT LANGUAGE="PerlScript"> </SCRIPT>
     
    Client-side PerlScript has the added requirement that both ActivePerl and PerlScript be installed on each computer will will be loading PerlScript pages.

    So I guess the client browser isn't irrelavant, eh? If the poster meant server-side perlscript (and I misunderstood) then you are right and the poster needs to look at an ASP manual to get things working right

    theAcolyte

[reply]

In Section Seekers of Perl Wisdom