诊断“请求超时”HttpExceptions的任何进展？ [英] Any Progress on Diagnosing “Request timed out” HttpExceptions?

问题描述

我遇到与本文所述相同的问题，诊断请求超时 HttpExceptions 。我按照建议打开了失败的请求跟踪，并且正在和MS的某个人一起工作（虽然它很慢）。

I am having the same issue as described in this post, Diagnosing "Request timed out" HttpExceptions. I've turned on Failed Request Tracing as recommended and am working with someone at MS (although it's painfully slow).

原始帖子在一年多内没有更新，所以我想知道是否找到了修复程序，或者你是否只是忽略了这些错误。

The original post hasn't been updated in over a year, so I'm wondering if a fix was ever found or if you're just ignoring these errors.

任何帮助都将不胜感激。

Any help would be appreciated.

推荐答案

经过七个多月的努力解决这个问题，微软的优秀人员终于找到了问题所在。它并没有最终成为一个复杂的问题，我们当然都学到了很多关于IIS 7+集成模式的知识。

After over seven months of troubleshooting this issue, the fine folks at Microsoft finally tracked down the problem. It didn't end up being that complicated an issue, we all certainly learned a lot about IIS 7+ integrated mode.

总结：

在IIS6& IIS7 +经典模式，在读取整个实体主体之前，请求不会到达asp.net。如果实体主体没有被完全读取，那么从未到达过asp.net，因此http只记录错误，而asp.net永远不会更明智。

In IIS6 & IIS7+ Classic mode, the request doesn’t reach asp.net until the entire entity body is read. If the entity body doesn’t get completely read, asp.net has never been reached so http just logs the error and asp.net is never the wiser.

但是，在IIS7 +集成模​​式下，asp.net立即获取请求，因此如果实体主体没有完全读取，asp.net会记录超时并触发异常。

However, in IIS7+ Integrated mode, asp.net picks up the request immediately, so if the entity body doesn’t get completely read, asp.net logs the timeout and triggers the exception.

因此，可以安全地忽略这些异常，因为它们是预期的行为。

So, these exceptions can safely be ignored because they are expected behavior.

我真的希望这可以帮助其他人。

I really hope this helps someone else out there.

这篇关于诊断“请求超时”HttpExceptions的任何进展？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！