Application mapping - how can I dig deeper?
From: Benman (bmannino_at_gmail.com)
Date: 02/16/05
- Next message: Dan: "search returns no summary available"
- Previous message: Dan: "Index server returning file:///d:\..... Instead of URL?"
- Next in thread: David Wang [Msft]: "Re: Application mapping - how can I dig deeper?"
- Reply: David Wang [Msft]: "Re: Application mapping - how can I dig deeper?"
- Messages sorted by: [ date ] [ thread ]
Date: 16 Feb 2005 09:00:51 -0800
Hi,
I have been wrestling with IIS6 for some time now trying to figure out
my missing link.
I posted a question about 2 weeks ago, and the answer helped me get to
where I am now.
Our dBASE executable files (.DBW extension) were generating 404 Errors
before any Web Service Extensions were added. For testing purposes, I
changed the default 'Prohibit' setting for 'All Unknown CGI Extensions'
to 'Allow' and the .DBW file executed perfectly.
Just to paint a more complete picture, the .dbw was generated by dBASE
to add records to a simple table and output an HTML result.
All the necessary files were placed into the wwwroot folder of the
Win2K3 web server. Client browsers then pointed to
http://WEBSERVER/webtest.htm and users enter table data into a form.
This form then does a POST submission to 'webtest.dbw' in the same
wwwroot directory.
I would like to beef up the security by only allowing the dBASE runtime
to be executed. When I add a web service extension pointing to the
dBASE runtime executable (D:\Program
Files\dBASE\PLUS\Runtime\PLUSRun.exe) and set it to 'Allow' after
restoring all the other CGIs to their default 'Prohibit' setting, I get
the same 404 error.
I'm definitely missing something, but not sure exactly what it could
be.
In the IIS Manager default web site properties, I did map the .dbw
extension to the specific target:
"D:\Program Files\dBASE\PLUS\Runtime\PLUSRun.exe" "%s"
for all verbs as specified in the dBASE web connection documentation.
So my best assumption here is that the .dbw invokes other executables
besides the PLUSRun.exe. Since they are not listed in this web service
extension, it fails with the 404 error. This is the only thing that
makes sense to me why this fails, and 'All Unknown CGI Extensions'
works fine.
Is there any way to dig deeper into IIS (log files somewhere?) that
could tell me what other executable files it may be looking for?
Any help would be greatly appreciated.
- Next message: Dan: "search returns no summary available"
- Previous message: Dan: "Index server returning file:///d:\..... Instead of URL?"
- Next in thread: David Wang [Msft]: "Re: Application mapping - how can I dig deeper?"
- Reply: David Wang [Msft]: "Re: Application mapping - how can I dig deeper?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
