New Application Extension reports 404

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jim Frankland (PRIVATEjfrankland_at_PRIVATEacoffice.comPRIVATE)
Date: 09/06/04 

Date: Sun, 5 Sep 2004 19:37:46 -0500

Hi all,

I'm sure I'm missing a simple security setting somewhere.

Moving a site from a IIS4 server to IIS6 on W2K3. The original developer
used lots of different file extensions (I assume in an attempt to deter
hackers). For example he might call a form script called MYFORM.RUN or
SUBMITFORM.RUN. Neither of these filenames actually exist on the server,
but IIS4 had the "RUN" extension mapped to execute a predefined perl script.

In IIS6 I go into my directory properties and under the DIRECTORY tab I
created an Application Settings. Set it up for "Scripts and Executables"
and set my Application Pool. Then I went into CONFIGURATION... Under the
MAPPINGS tab I created a new extension of RUN. Under the executable path I
enter:

F:\Perl\bin\perl.exe "E:\Inetpub\myhostsite\functions\formscript.pl"

in the executable dialog. I made sure to REMOVE the check on the box VERIFY
THAT THE FILE EXISTS and limited it to GET, POST.

This is VERY SIMULAR to a WORKING perl script extension of:

Extension = .PL
Executable = F:\Perl\bin\perl.exe "%s" %s

I've tried eliminating the full path in the executable, since the
formscript.pl is located in the same directory as the form html code. I've
also tried ALL VERBS instead of the post/get limit.

Always the same effect... The browser reports 404 "directory or file does
not exist" error.
I can run the formscript.pl by entering it on the browser address line, so I
know it works and perl is functioning.

I'm sure there is a simple setting I am missing.
I saw a reference to WEB.CONFIG file in a BIN directory with code to <add
verb... for <httpHandlers... but I am not fully understanding this - it
might only be for ASPX?

Thanks in advance for help on these extensions.
(I know the simple answer may be to change all the HTM code to properly call
the perl scripts directly, but in thousands of pages - I'm sure to miss
something. I already have a list of all these funny extensions and
executables from the IIS4 server.)

Relevant Pages

  • Re: New Application Extension reports 404
    ... Substatus code for these 404 requests - that will help diagnose the problem. ... > This is VERY SIMULAR to a WORKING perl script extension of: ... > Thanks in advance for help on these extensions. ... > executables from the IIS4 server.) ...
    (microsoft.public.inetserver.iis)
  • Re: creating stand-alone extended tclsh
    ... You're right, more Tclers enjoy flexibility offered by dynamically loading extensions, and this is probably good way to go when running on a single machine. ... With static linking this is a problem, with dynamic loading Tcl will load the correct version in for you automatically. ... a simple solution to tag executables, ...
    (comp.lang.tcl)
  • RE: File extensions spoofable in MSIE download dialog
    ... File extensions spoofable in MSIE download dialog ... allows executables to run as soon as a user has elected to open what ... provided in the link over the filename suggested by the header's filename ... Here is the ASP equivalent code to StatiC's php tidbit (tested under both ...
    (Bugtraq)
  • Re: Monkeypatching is Destroying Ruby
    ... caller at all, and import-module doesn't either. ... What am I missing? ... ability for an extended class to *always* appear extended when ... called from anywhere in a class that knows about those extensions, ...
    (comp.lang.ruby)
  • Application Mapping - IIS Config
    ... I'm trying to add some extensions to IIS on the properties, home directory, ... I must be missing something because the OK button is always disabled ... ...
    (microsoft.public.dotnet.framework.aspnet)