生产服务器上的 asp.net 调试
我们最近在生产服务器上部署了一个 ASP.Net 应用程序，但在 IE 中遇到了一些问题。 我们构建了一个基于 cookie 的自定义安全模块。 有趣的是，在所有浏览器中的临时服务器上一切都完美运行，它也适用于生产服务器，但仅适用于 Firefox。 该进程能够写入 cookie，但由于某些奇怪的原因，当从生产服务器上的 IE 登录时，身份验证无法读取 cookie。 安全模块是由另一家公司开发并移交给我们的，有趣的是该公司现在已经解散，没有人可以对整个模块进行一些知识共享。
你们建议如何在生产服务器上调试/解决该问题。
We have recently deployed an ASP.Net application on Production server and are having some trouble with it in IE. We have built a custom security module based on cookies. The interesting part is, everything works perfect on staging server in all browsers and it also works on Production server but ONLY for Firefox. the process is able to write the cookie but for some weird reason the authentication is unable to read the cookie when logged in from IE on production server. The security module was developed by another company and handed over to us, interestingly that company has now been dissolved and there is nobody who could do some knowledge sharing on the overall module.
how would you guys recommend to debug/troubleshoot the issue on production server.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
尝试在网站上输入 ELMAH。 安装非常非侵入性，您可以很快得到一些答案。
如果这不能满足您的需要（这可能是由于 cookie 问题而发生），请尝试获取调试栏类型的应用程序并逐步完成该过程。
如果您仍然遇到问题，您可能需要使用 log4net 之类的东西来注入一些额外的内容调试详细信息并查看结果，但这将需要您重新编译应用程序并将其迁移。
Try dropping in ELMAH on the site. Installation is pretty non-invasive and you can get some answers really fast.
If that isn't giving you what you need, which may occur thanks to cookie issues, try getting a debugbar type app and walk through the process.
If you're still running into issues, you may need to use something like log4net to inject some additional debug details and view the results, but this will require you to recompile the app and migrate it up.
您应该做的第一件事绝对是让您的登台服务器准确镜像您的生产服务器。 例如，如果生产服务器不在您的主域中，那么临时服务器也不应该在那里。
如果您的 IE 遇到问题，那么听起来安全区域是不同的。 这可能是由域名问题等“小事情”引起的。
从硬件到服务包级别，再到安装的软件，一切都应该完全相同。 如果它们不是这样弹出的东西。
一旦您可以在暂存中复制问题，然后，只有到那时，才能修复它。 调试生产是个坏主意。
The absolutely first thing you should do is make your staging server mirror your production server exactly. For example, if the production server is NOT in your primary domain, then the staging server shouldn't be there either.
If you are having problems with IE, then it sounds like the security zones are different. This can be caused by "little things" like the domain issue.
Everything from hardware, to service pack levels, to installed software absolutely should be identical. If they aren't things like this pop up.
Once you can replicate the problem in staging then, and only then, fix it. Debugging production is Bad Idea.