Subject: From: Date:

Re: [ECS] PERL Problem Ingo Pakleppa Thu, 02 Mar 2000 13:03:20 -0800

---

Ooopsss. You are right, I missed that. Would have been unusual to begin 
with to execute a perl script on the client side.

Then, you would have to tell PWS to use Active Perl to execute a .pl file. 
I'm not sure how to do that in PWS. Otherwise, PWS would treat it as a 
regular data file and try to upload it to the client - which is what is 
happening.

Is the script in a directory marked executable on the server, in PWS? 
Usually, this might be the directory /cgi-bin or /bin. If the directory is 
not marked as executable, again, PWS would treat the file as a data file 
and try to upload it to the client.

Ingo

At 09:48 AM 3/2/00 -0500, Scott Reston wrote:
>actually, i don't think this is the case. the configuration is all on the 
>server. the script itself never gets downloaded to the client - the line 
>in kevin's script that
>reads:
>
>print "Content-type: text/html\n\n";
>
>tells the browser that the mime-type for the incoming file is HTML... the 
>server just needs to know that this is a script and should be executed...
>
>scott reston
>ih8gates@concentric.net
>http://www.indelible-blue.com/meetib/scott/
>
>
>On Thu, 02 Mar 2000 06:22:24 -0800, Ingo Pakleppa wrote:
>
> >This problem could originate from both the client and the server.
> >
> >The server must be configured to send the correct mime-type (I don't know
> >it, but it might be text/perl or something like that). In most servers, you
> >would actually associate the extension .pl with the mime-type. I believe
> >PWS uses the mime-type that you enter in Explorer's file associations.
> >
> >And the browser must be configured to run Active Perl as a helper
> >application when this mime type is received.
> >
> >Ingo

---