If the user does not want to replace all .asp files to
point to the php processor, then an isapi filter not
extension would be the choice. Filters sit above any
extension and will receive the request first. In that
request you would then remap file.asp to point to file.php.
I wouldnt consider this overkill considering you could
probably do this in under 20 lines of code.
See:
http://www.codeproject.com/isapi/isapiredirector.asp
or for a comprehensive list:
http://www.iisfaq.com/Default.aspx?tabid=3194
On Tue, 15 Feb 2005 10:55:34 +1100
"Ken Schaefer" <Ken@adOpenStatic.com> wrote:
ASP files (.asp .asa etc) are handled by an ISAPI
Extension, not an ISAPI
Filter, so I'm not sure what you mean by setting a
filter. Certainly you
could write your own filter to look at incoming requests
and rewrite them (or
similar), but that would probably be overkill (there are
some 3rd party ISAPI
filters that do this)
FWIW:
PHP (.php) can be setup either as an ISAPI Extension or
as CGI (check
www.visualwin.com for instructions)
Cheers
Ken
: -----Original Message-----
: From: Cory Foy [mailto:Cory.Foy@mobilehwy.com]
: Subject: Re: force extention handling in IIS?
:
: In your ISAPI Filters, can't you just set up a filter
for file.asp and
: have it point to the PHP ISAPI, instead of doing *.php
or some other
: wildcard?
:
: Cory
:
: Ken Schaefer wrote:
: > Neither of these two things will work.
: >
: > a) Server.Transfer() will attempt to run the page
using the ASP engine.
The
: > ASP ISAPI extension doesn't understand PHP
: >
: > b) That affects all .asp pages (as you note), but OP
says that he can't
: > change the setting for all ASP pages (yet). However,
this setting is
actually
: > on an Application by Application basis. You can
create a new web
application
: > at any folder level in the web root hierarchy via the
IIS Manager. So, if
you
: > convert an entire folder worth of files, you could
remap .asp -> PHP
ISAPI
: > extension on a folder-by-folder basis.
: >
: > One could use redirects, but I hear that you get
penalised by search
engines
: > if you do that sort of thing on a massive scale.
: >
: > Cheers
: > Ken
: >
: > : -----Original Message-----
: > : From: Damhuis Anton [mailto:DamhuisA@aforbes.co.za]
: > : Sent: Monday, 14 February 2005 5:29 PM
: > : To: webappsec@securityfocus.com
: > : Subject: RE: force extention handling in IIS?
: > :
: > :
: > : I have never tried it, but maybe a Server.Transfer
to the PHP page?
: > :
: > : With Server.Transfer the client still sees the
original page (.asp) but
it
: > will be
: > : processed but the second page.
: > :
: > : Another option is to change the engine reference in
IIS
: > :
: > : Open IIS
: > : Right Click your WEBSite,
: > : Select 'Home Directory' tab.
: > : Click Configuration button.
: > : In Application Mappings List select .asp
: > : Click Edit.
: > : Enter the PHP Engine Dll Name in executable text
box.
: > :
: > : This will make sure that ALL .asp extensions in the
selected web site
will
: > use the
: > : PHP Engine.
: > :
: > : Regards
: > : Anton
: > :
: > : -----Original Message-----
: > : From: Leigh Morresi
[mailto:leighm@linuxbandwagon.com]
: > : Sent: 14 February 2005 01:29
: > : To: webappsec@securityfocus.com
: > : Subject: force extention handling in IIS?
: > :
: > :
: > : Hi there
: > :
: > : Trying to fix some loose ends by initally rewriting
a couple of ASP
: > : scripts as PHP
: > : is it possible to force IIS (6.0) to run a file.asp
with PHP? i cant
: > : change the filename because
: > : we have a lot of clients with some 3rd party
applicaiton that is
: > : connecting to the "file.asp"
: > :
: > : IIS will let me run PHP scripts and set the file
extention but not on a
: > : per-filename basis
: > :
: > : any ideas?
: > :
: > : leigh
---------------------------------------------------------------------
Web mail provided by NuNet, Inc. The Premier National provider.
http://www.nni.com/
