ISAPI 扩展在 IIS7 上给出 404
我正在运行 Windows 7 64 位并尝试加载我正忙于在本地 IIS7 计算机上编写的 ISAPI 扩展。
- 我将位置添加到“ISAPI 和 CGI 限制”下的 DLL
- 我使应用程序池识别 32 位应用程序（扩展是用 Delphi 编写的）
- 我确保“每个人”对目录/dll 具有完全权限
- 我确保“允许“处理程序映射”部分中的 ISAPI-dll 并将其设置为“读取/脚本/执行”权限
我在 IIS7 中仍然收到 404.0 错误
我已检查我的 MIME 映射是否设置为处理*.dll 和我有一个在同一台计算机上的不同站点上运行的完美工作 ISAPI 扩展。
我什至把这个给我带来 404 的 ISAPI 扩展放在工作网站的根目录中（另一个 DLL 所在的位置），并将“ISAPI 和 CGI 限制”重新映射到它。仍然给我 404.0，即使我实际上可以同时或之后直接运行另一个 DLL，这很好。
知道 WTF 发生了什么吗？
I'm running windows 7 64-bit and trying to load an ISAPI Extension I'm busy writing on my local IIS7 machine.
- I added the location to the DLL under "ISAPI and CGI Restrictions"
- I made the application pool recognize 32-bit applications (Extension is written in Delphi)
- I made sure "Everyone" has full permissions on the directory/dll
- I made sure to "Allow" ISAPI-dll in the "Handler Mappings" section and set it to "Read/Script/Execute" permissions
I still get 404.0 error in IIS7
I have checked that my MIME Mapping's is setup to handle *.dll and I have a perfectly working ISAPI-extension running on a different site on the same machine.
I even took this ISAPI-extension that gives me the 404 and put it in the root of the working website (where the other DLL is) and re-mapped the "ISAPI and CGI Restrictions" to it. Still gives me 404.0, even though I can literally run the other DLL at the same time or directly afterward and it's fine.
Any idea WTF is going on?!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
事实证明，当您在设置其他所有内容以使其正常工作时收到 404.0 文件未找到错误时，这意味着您正在使用的 ISAPI 扩展也引用（即包含）另一个 DLL。如果没有该 DLL，它将出现 404.0
另外，如果您忘记“允许”特定的 ISAPI DLL（即使允许执行 ISAPI/CGI），您将收到的错误消息是 404.2 :)
It turns out when you receive a 404.0 file not found error when you've setup everything else to work correctly, it means thats the ISAPI extension you're using is referencing (ie, including) another DLL as well. Without that DLL, it will 404.0
Also, if you've forgotten to "allow" a specific ISAPI DLL (even though ISAPI/CGI is allowed to execute) the error message you'll get is 404.2 :)
我知道这个问题已经得到解答，但由于我昨天刚刚遇到这个问题，我还要指出，如果应用程序目录没有执行权限，您会得到 404.0 响应。这不仅仅是针对绑定错误。
I know this one's been answered but since I just ran across this yesterday, I'd also point out that 404.0 is the response you get if the application directory doesn't have Execute permission on it. It's not just for binding errors.
对于 64 位，问题在于注册表：我对于 32 位的问题是注册表中 apache 重定向器的位置是： [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0]
但对于 64 位位置必须是： [HKEY_LOCAL_MACHINE \SOFTWARE\Wow6432Node\Apache Software Foundation\Jakarta Isapi Redirector\1.0]
注意“Wow6432Node”。
因此，只需在 Wow6432Node 上重新创建 32 位，然后就可以了。
For 64 bit, the problem is the registry: The problem I was for 32 bit the location of apache redirector in registry is: [HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\1.0]
but for 64 bitlocation must be: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Jakarta Isapi Redirector\1.0]
Note the "Wow6432Node".
so just re-create the 32 bit on the Wow6432Node and then you are set.