1

在本地，映射到 IIS 中的虚拟目录，一切正常。当我将站点部署到 Azure 时，我仍然可以访问 Glimpse.axd 并设置 cookie（报告的 IP 在允许列表中），但 Glimpse 图标未显示在任何页面上。

浏览器没有报告任何 javascript 错误。检查页面源，应该在正文末尾注入页面的两个 javascript 包含文件没有被发送。

在 web.config 中设置loggingEnabled="true"会在本地生成相同的日志，它可以工作，就像它在 Azure 上一样，它不起作用（虚拟目录和 requestId 除外）。从 Azure 日志：

2012-09-25 17:54:13.0271|INFO|Glimpse.Core.Module|BeginRequest handling complete for requestId 4da70989-d89b-46ef-80c6-43bd6f5a7ce1 (/cart)|
2012-09-25 17:54:13.1571|WARN|Glimpse.Mvc3.Plugin.Execution|get_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:13.1571|WARN|Glimpse.Mvc3.Plugin.Execution|set_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:13.1571|WARN|Glimpse.Mvc3.Plugin.Execution|GetType method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:13.1571|WARN|Glimpse.Mvc3.Plugin.Execution|MemberwiseClone method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:28.5420|WARN|Glimpse.Mvc3.Plugin.Execution|get_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:28.5420|WARN|Glimpse.Mvc3.Plugin.Execution|set_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:28.5420|WARN|Glimpse.Mvc3.Plugin.Execution|GetType method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:28.5420|WARN|Glimpse.Mvc3.Plugin.Execution|MemberwiseClone method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5812|WARN|Glimpse.Mvc3.Plugin.Execution|get_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5812|WARN|Glimpse.Mvc3.Plugin.Execution|set_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5812|WARN|Glimpse.Mvc3.Plugin.Execution|GetType method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5831|WARN|Glimpse.Mvc3.Plugin.Execution|MemberwiseClone method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5831|WARN|Glimpse.Mvc3.Plugin.Execution|get_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5831|WARN|Glimpse.Mvc3.Plugin.Execution|set_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5831|WARN|Glimpse.Mvc3.Plugin.Execution|GetType method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5831|WARN|Glimpse.Mvc3.Plugin.Execution|MemberwiseClone method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5988|WARN|Glimpse.Mvc3.Plugin.Execution|get_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5988|WARN|Glimpse.Mvc3.Plugin.Execution|set_Binders method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5988|WARN|Glimpse.Mvc3.Plugin.Execution|GetType method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.5988|WARN|Glimpse.Mvc3.Plugin.Execution|MemberwiseClone method of System.Web.Mvc.ControllerActionInvoker type is not proxyable.|
2012-09-25 17:54:30.7874|INFO|Glimpse.Core.Module|PostRequestHandlerExecute handling complete for requestId 4da70989-d89b-46ef-80c6-43bd6f5a7ce1 (/cart)|
2012-09-25 17:54:30.8978|INFO|Glimpse.Core.Module|PostReleaseRequestState handling complete for requestId 4da70989-d89b-46ef-80c6-43bd6f5a7ce1 (/cart)|
2012-09-25 17:54:31.0277|INFO|Glimpse.Core.Module|Glimpse JSON payload created for requestId 4da70989-d89b-46ef-80c6-43bd6f5a7ce1 (/cart)|
2012-09-25 17:54:31.1411|INFO|Glimpse.Core.Module|Glimpse output generated for requestId 4da70989-d89b-46ef-80c6-43bd6f5a7ce1 (/cart)|
2012-09-25 17:54:31.1411|INFO|Glimpse.Core.Module|RequestId 4da70989-d89b-46ef-80c6-43bd6f5a7ce1 (/cart) persisted|
2012-09-25 17:54:31.1411|INFO|Glimpse.Core.Module|EndRequest handling complete for requestId 4da70989-d89b-46ef-80c6-43bd6f5a7ce1 (/cart)|

去年，我在开发中成功使用了 Glimpse，并部署到了 Azure 上的测试服务器。从那时到现在，我都不需要使用它。该项目发生了很多变化，但这是一年前有效的解决方案。我只是想找出目前仅在 Azure 中出现的问题。

关于我可以从哪里开始寻找的任何建议？我正在使用带有 Glimpse 0.87 的 MVC3 和 .NET 4.0

4

1 回答 1

0

I'm willing to bet that the IP address you have configured in web.config is not the actual IP address Azure's infrastructure passes through.

The good news is, we have removed the IP filtering feature from the Glimpse 1.0 release candidate, which is currently available as a prerelease package on NuGet.

If you continue to have issues after upgrading, please submit a bug report on Glimpse's GitHub issue tracker.

于 2012-12-13T00:03:33.473 回答