David
Fri Jun 22 21:09:08 CDT 2007
1. With a relative path as action, you assume the browser POSTs back
to your DLL
2. If POST is to a DLL, the vdir must have Execute Permissions to
"Scripts and Executables". Otherwise, IIS considers it a POST to a
static file with .dll extension and you still get 405.
As to why a .DLL is not automatically treated as executable ISAPI code
-- The notion of "code execution" needs to be different in the URL
namespaces hosted by IIS and the filesystem namespace hosted by the
OS.
The reason this is different is simple: Suppose you wanted to
distribute a self-extracting EXE file for download by customers via
Web Browser contacting IIS. If IIS does NOT have a different notion of
"code execution" than the OS, IIS would be running the EXE on the
server (since EXE is considered executable code) instead of sending
the EXE to the client as a download. Clearly, that is not what you
want because you want the self-extracting EXE to be downloaded by
potential customers.
And the IIS configuration which determines how IIS defines the notion
of "code execution" ? It's the "Execute Permissions" setting.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Jun 22, 5:26 pm, usfinecats <usfinec...@nospam.nospam> wrote:
> Newbie question
>
> On XP PRO I have a small simple web page that will call into an ISAPI
> extension to be found in the same directory. In an html page I have a form I
> have:
>
> <form action="MyExtension.dll" method="POST">
>
> that posts a request to my MyExtension.dll
>
> The browser returns with 405, and the error message
>
> "The page you are looking for cannot be displayed because the page address
> is incorrect. " but I know the dll is there
>
> any ideas about how I need to set up IIS? and the virtual directories?
>
> --
> Gak -
> Finecats