OT: question

[Fairlight]

Simon--er, no...it was Brian K. White--said:
> On 4/9/2010 7:41 PM, Fairlight wrote:
> 
> > And yet, every IIS installation I've ever seen has a cgi-bin already good
> > to go, stock.
> 
> I believe you entirely, but just for the record
> 
> http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/bc0c4729-e892-4871-b8f3-fcbf489f2f09.mspx?mfr=true
> 
> says otherwise.
> 
> I've never used it myself, which means you've seen infinitely more 
> installs than I have, so whether this doc lies or only applies to a 
> small fraction of installs or is simply too old or maybe there is an 
> install doc or recipe that everyone follows which includes setting up 
> cgi or ??... All I'm doing is pointing at what MS themselves say on the 
> subject.

Fair enough.  It wouldn't be the first time the docs for something were
wrong/incomplete/outdated and didn't mesh with reality. 

Dunno about "infinitely", but there are at least four IIS installs that
I've seen.  Four is a relatively finite number.  :)

I'd think that maybe the docs were right, if I hadn't worked on systems
where cgi-bin was in already place and there had been nobody that touched
the system that would even know what cgi-bin is, much less how to
configure it to sane defaults.  But I have seen such things under those
circumstances...  In fact, those docs may very well be outdated, as the
steps that one has to take to run Perl CGI programs under IIS (which are
documented in numerous places online) are really mostly obsolete.  The most
I've had to do in recent times was change the user under which the programs
run--everything else has been in place--and that was only to make things
mesh with filePro, which was installed in such a way that the change was
necessary.

mark->
-- 
Audio panton, cogito singularis,