Re: New Application Extension reports 404
From: Ken Schaefer (kenREMOVE_at_THISadOpenStatic.com)
Date: 09/06/04
- Next message: Ken Schaefer: "Re: HOW TO Restrict FileSystemObject (fso) to ASP context"
- Previous message: Ken Schaefer: "Re: host header does not seem to work in Server 2003"
- In reply to: Jim Frankland: "New Application Extension reports 404"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 6 Sep 2004 13:30:43 +1000
Hi,
Please look in the IIS logfile for this website, and tell us the HTTP
Substatus code for these 404 requests - that will help diagnose the problem.
Cheers
Ken
"Jim Frankland" <PRIVATEjfrankland@PRIVATEacoffice.comPRIVATE> wrote in
message news:uo2i1n6kEHA.596@TK2MSFTNGP11.phx.gbl...
> 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.)
>
>
>
- Next message: Ken Schaefer: "Re: HOW TO Restrict FileSystemObject (fso) to ASP context"
- Previous message: Ken Schaefer: "Re: host header does not seem to work in Server 2003"
- In reply to: Jim Frankland: "New Application Extension reports 404"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
