Thanks, This demonstrates a very important point with CGI--whenever possible, one should use relative paths--and never use backslash-delimited paths in a URL, regardless of OS. Web servers will translate to the local delimiters transparently.
Joseph [EMAIL PROTECTED] wrote: > I believe in the new example the browser is not passing the form to any server >because it is not a relative path, nor does it begin with a protocol specifier, and >it recognizes C: as something it can handle. Try specifying either a relative path >or using a full URL with something like http://localhost/path/script.cgi or >http://127.0.0.1/path/script.cgi. > > Yeh the CGI list is kinda slow for the last few. A lot of us are on both lists and >saw the thread originally appeared on the main list. (That and I have no experience >admining IIS ;-)) > > http://danconia.org > > ------------------------------------------------ > On Wed, 8 Jan 2003 08:29:11 -0500, "Paul Kraus" <[EMAIL PROTECTED]> wrote: > > > Ok following these instructions. > > > > Now if I call a script http://localhost/path/myscript.cgi||.pl > > It will run the script just likes it is supposed to. > > > > When I call the scripts from a form with this command. > > <form method="POST" name="Form 1" > > action="c:\inetpub\wwwroot\test\cgi\count.cgi"> > > then the pl file tries to download and the cgi file still displays the > > source. > > > > Where getting closer :) > > > > FYI I tried directing this to the cgi list but its seems to be very low > > traffic. 4 messages in two days. > > > > > -----Original Message----- > > > From: R. Joseph Newton [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, January 07, 2003 10:46 PM > > > To: Paul Kraus > > > Cc: [EMAIL PROTECTED]; Perl > > > Subject: Re: Cgi Win xp Perl > > > > > > > > > Hi Paul, > > > > > > Did you set up IIS for the virtual directory? You need top > > > add a virtual directory for each location you'll be serving > > > these scripts up from. File-system opening will not work as > > > it does with static HTML. 1. Create a virtual directory in > > > IIS 2 Right-click on it, and choose properties 3. Click > > > configure 4. Make sure that *.pl and *.cgi are listed as file > > > types for the server to handle. The path to the executable > > > should be followed by " %s %s", like: f:\Perl\bin\perl.exe %s > > > %s 5. Hake sure All Verbs is selected 6. Use the > > http://localhost/path URL format to access your script > > > > Joseph > > > > > > Paul Kraus wrote: > > > > > nope that's the stumper. I use Perl all the time for business and just > > > > > to play around I wanted to mess with cgi. The non cgi stuff works > > > fine. Actually I can ran the cgi stuff from the command line just fine > > > > > to. > > > > > > > -----Original Message----- > > > > From: david [mailto:[EMAIL PROTECTED]] > > > > Sent: Tuesday, January 07, 2003 4:49 PM > > > > To: [EMAIL PROTECTED] > > > > Subject: RE: Cgi Win xp Perl > > > > > > > > > > > > Paul Kraus wrote: > > > > > > > > > same issues. If it's a pl file it tries to download. If its > > > > .cgi then > > > > > it just displays my code. > > > > > > > > > > > > > what happen if you type your cgi_script.pl in the DOS prompt? does > > > > Windos complain about not able to execute the script? if so, > > > > Windos(as well as > > > > IIS) probably doesn't know how to execute your *.pl file. you > > > > probably have > > > > to associate *.pl with your Perl binary. > > > > > > > > david > > > > > > > > -- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > -- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
