%1 is not a valid Win32 application?

Just a quick update:

I decided to rename the extension for python scripts ".pycgi". Ok, so
when I did so, I decided to test. Result: with .pycgi in the IIS Admin
properties, test.cgi STILL returns "%1 is not a valid Win32
application." Wow. So it's like IIS is ignoring the .cgi rule I added
somehow.

Second, once I renamed test.cgi to test.pycgi, the file time is totally
unrecognized. My browser (Mozilla) declares the type of test.pycgi to
be unrecognized and askes me if I want to download instead. I even
added the .pycgi rule to the vitual directory where the script lives and
I get the same result.

Help!
 >> Stay informed about: %1 is not a valid Win32 application? 

Update #2:

Renamed the extension yet again, this time to .py. Mozilla seems to
recognize this as a text file and displays it, but IIS still doesn't
seem to catch the .py rule I added to the IIS Admin properties. The
script is still not being executed.

Win2K Pro, IIS 5.0. SP4 and current on all updates.

Man I hope someone can help, I'm really lost here. I think I'll try to
add perl as a script just to see if I can get it to work.
 >> Stay informed about: %1 is not a valid Win32 application? 

Argh. Well I found it but I'm not happy.

1. Adding a script to IIS Admin does NOT add the defintition for the
whole server. I had to add it to the virtual directory, and since I have
to add it to EVERY virtual directory (it appears) I am unhappy with IIS 5.0

2. There was a SECOND problem where a script executed by IIS would be
passed parameters like:

d:\Python23\python.exe D:\Documents and Settings\mark\Web\test.py

which of course the python.exe sees as THREE PARAMETERS!!!

AAAAAAAARRRRRRRRRRRRGGGGGGGGGGGGGGGGHHHHHHHHHHHHHH!!!!!11!!!ELEVEN

Dear folks at MS, this sucks. I can't control this. Unless you want to
make spaces in filenames illegal (fat chance), you have to help me out
when there are spaces in the SINGLE PARAMETER that YOU pass to me.

I can fix this with setting the script path in IIS to:
d:\Python23\python.exe "%s" %s

Notice the quotes around the first %s parameter. This works but is it
garanteed? What about the second parameter, will there be an case where
it fails for lack of quotes?

I feel that if IIS is passing a path, and it's got spaces, then IIS
ought to add the quotes on it's own. Seriously. What command could
possibly tell that those three things on the command line are really
supposed to be one? Only IIS knows this (or any caller, but here we are
discussing IIS).

Please add the quotes guys. Seriously: who do I submit a bug report to?
This needs to be changed.


Ok. Whew. Rant off, thanks for listening.
 >> Stay informed about: %1 is not a valid Win32 application? 

Add a Application Extension of ".py" (or .pycgi, or .cgi -- it does not
matter to IIS) and for the ScriptEngine, give:
<full path to PYTHON.EXE> "%s" "%s"

..cgi, .dll, .exe, and .com are special extensions that IIS recognize and try
to execute. If you add an Application Extension that overrides these
extensions, IIS will treat them however you overrode it.

I suggest that you use ISAPI (DLL) versions of a ScriptEngine on IIS instead
of the CGI (EXE) version -- it'll most likely perform better as well as give
500 errors with Win32 error messages instead of a generic "%1 is not a valid
Win32 application".

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Mark Space" <mark_space44.DeleteThis@hotmail.com> wrote in message
news:voc786o8hfmlb0@corp.supernews.com...
Update #2:

Renamed the extension yet again, this time to .py. Mozilla seems to
recognize this as a text file and displays it, but IIS still doesn't
seem to catch the .py rule I added to the IIS Admin properties. The
script is still not being executed.

Win2K Pro, IIS 5.0. SP4 and current on all updates.

Man I hope someone can help, I'm really lost here. I think I'll try to
add perl as a script just to see if I can get it to work.
 >> Stay informed about: %1 is not a valid Win32 application? 

 > 1. Adding a script to IIS Admin does NOT add the defintition for the
 > whole server. I had to add it to the virtual directory, and since I have
 > to add it to EVERY virtual directory (it appears) I am unhappy with IIS
5.0

No, I think you have it misconfigured. IIS has an inheritance hierarchy for
configuration values -- values set at the root are inherited in the children
nodes unless the children nodes override it.

So, if you add .py at the global level, all websites which did not override
the script mapping would automatically inherit settings without a problem.
The UI will also warn you of which sites are overriding the global settings
when you're setting the value (it'll pop up a little dialog asking you
permission to override the setting on a list of websites).

If you're doing this via commandline/script, it is presumed that you are
advanced enough to be aware of the issues.


 > 2. There was a SECOND problem where a script executed by IIS would be
 > passed parameters like:
 >
 > d:\Python23\python.exe D:\Documents and Settings\mark\Web\test.py

 > Dear folks at MS, this sucks. I can't control this. Unless you want to
 > make spaces in filenames illegal (fat chance), you have to help me out
 > when there are spaces in the SINGLE PARAMETER that YOU pass to me.

 > I can fix this with setting the script path in IIS to:
 > d:\Python23\python.exe "%s" %s

Be safe. Put "" around both %s.

This is nothing special here -- this is exactly as Windows has always
behaved. Namely, spaces separate commandline parameters, unless you glob
the space together with a ". You will note that in Windows, " (double
quote) is an invalid filename...


 > I feel that if IIS is passing a path, and it's got spaces, then IIS
 > ought to add the quotes on it's own. Seriously. What command could
 > possibly tell that those three things on the command line are really
 > supposed to be one? Only IIS knows this (or any caller, but here we are
 > discussing IIS).

No. This is an issue ONLY because we're talking about CGI and there is
commandline parameter passing and globbing considerations. I think that it
is completely up to the user to delineate the proper commandline parameter
globbing when configuring the server. After all, given an arbitrary
sequence of words separated by spaces, it would be impossible for any
program to discern what is the executable, what is the path, and what is the
script. It is in the user's best interest to delineate those boundaries
correctly.

Incidentally, with an ISAPI (the preferred extension method of IIS), this is
completely a non-issue -- we took care of it by giving you one variable to
retrieve the script name.


 > Please add the quotes guys. Seriously: who do I submit a bug report to?
 > This needs to be changed.
You can try to file a bug during the public beta, but I am doubtful of this
request. IIS is absolutely not going to parse the commandline and insert
stuff for you. As soon as we start doing that, it opens up an avenue of
canonicalization attacks -- the liability is not worth the gains. This
would also open up potential bugs with existing scriptmappings that already
have "%s".

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: %1 is not a valid Win32 application? 

Just a note on the spaces in parameters - neither Windows nor *nix based
systems will parse your example correctly, you need to use quotes to mark a
single parameter with spaces in it no matter what the OS.

Jerry

"Mark Space" <mark_space44 DeleteThis @hotmail.com> wrote in message
news:vocbdrmdn3aa3d@corp.supernews.com...
 > Argh. Well I found it but I'm not happy.
 >
 > 1. Adding a script to IIS Admin does NOT add the defintition for the
 > whole server. I had to add it to the virtual directory, and since I have
 > to add it to EVERY virtual directory (it appears) I am unhappy with IIS
5.0
 >
 > 2. There was a SECOND problem where a script executed by IIS would be
 > passed parameters like:
 >
 > d:\Python23\python.exe D:\Documents and Settings\mark\Web\test.py
 >
 > which of course the python.exe sees as THREE PARAMETERS!!!
 >
 > AAAAAAAARRRRRRRRRRRRGGGGGGGGGGGGGGGGHHHHHHHHHHHHHH!!!!!11!!!ELEVEN
 >
 > Dear folks at MS, this sucks. I can't control this. Unless you want to
 > make spaces in filenames illegal (fat chance), you have to help me out
 > when there are spaces in the SINGLE PARAMETER that YOU pass to me.
 >
 > I can fix this with setting the script path in IIS to:
 > d:\Python23\python.exe "%s" %s
 >
 > Notice the quotes around the first %s parameter. This works but is it
 > garanteed? What about the second parameter, will there be an case where
 > it fails for lack of quotes?
 >
 > I feel that if IIS is passing a path, and it's got spaces, then IIS
 > ought to add the quotes on it's own. Seriously. What command could
 > possibly tell that those three things on the command line are really
 > supposed to be one? Only IIS knows this (or any caller, but here we are
 > discussing IIS).
 >
 > Please add the quotes guys. Seriously: who do I submit a bug report to?
 > This needs to be changed.
 >
 >
 > Ok. Whew. Rant off, thanks for listening.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: %1 is not a valid Win32 application? 

Hi Mark,

a) Settings are inherited. If you set something at the root level of a
website, it'll be inherited down. The exception is if you have a new web
application. When you create a virtual directory, it's marked as a new web
application root. You can remove this via the IIS MMC Snapin (there's a
"remove" button on the Home Directory tab), and then you vdirectory will
inherit settings from the parent folders, all the way up to the website
root.

b) WRT to spaces - you always need to use " around filepaths that contain
spaces (in the Windows world). This has been the case since Windows95
(regardless of whether you're scriping, programming or just writing batch
files). The alternative is to use the "truncated" 8.3 name (eg
c:\docume~1\mark\web\test.py) if you are supplying the actual argument.

That said, my advice is just to put things into folders that don't have
spaces in the first place - it'll save you hassles down the road.

Hope that helps.

Cheers
Ken

"Mark Space" <mark_space44.TakeThisOut@hotmail.com> wrote in message
news:vocbdrmdn3aa3d@corp.supernews.com...
: Argh. Well I found it but I'm not happy.
:
: 1. Adding a script to IIS Admin does NOT add the defintition for the
: whole server. I had to add it to the virtual directory, and since I have
: to add it to EVERY virtual directory (it appears) I am unhappy with IIS
5.0
:
: 2. There was a SECOND problem where a script executed by IIS would be
: passed parameters like:
:
: d:\Python23\python.exe D:\Documents and Settings\mark\Web\test.py
:
: which of course the python.exe sees as THREE PARAMETERS!!!
:
: AAAAAAAARRRRRRRRRRRRGGGGGGGGGGGGGGGGHHHHHHHHHHHHHH!!!!!11!!!ELEVEN
:
: Dear folks at MS, this sucks. I can't control this. Unless you want to
: make spaces in filenames illegal (fat chance), you have to help me out
: when there are spaces in the SINGLE PARAMETER that YOU pass to me.
:
: I can fix this with setting the script path in IIS to:
: d:\Python23\python.exe "%s" %s
:
: Notice the quotes around the first %s parameter. This works but is it
: garanteed? What about the second parameter, will there be an case where
: it fails for lack of quotes?
:
: I feel that if IIS is passing a path, and it's got spaces, then IIS
: ought to add the quotes on it's own. Seriously. What command could
: possibly tell that those three things on the command line are really
: supposed to be one? Only IIS knows this (or any caller, but here we are
: discussing IIS).
:
: Please add the quotes guys. Seriously: who do I submit a bug report to?
: This needs to be changed.
:
:
: Ok. Whew. Rant off, thanks for listening.
:
 >> Stay informed about: %1 is not a valid Win32 application?