[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 555
  • Last Modified:

Request timed out vs. Timeout Expired

I've recently started sporadically receiving the exception "Request timed out" on my chart aspx pages, and there's no stack trace to go with it.  What's odd about this is if I immediately refresh the page it works.
I'm accustomed to seeing "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding" when I've written a page that takes too long to load.

So my question is:
What's the difference between "Request timed out" and "Timeout Expired", and does anyone have any ideas what could be causing this?

Any help would be greatly appreciated.
1 Solution
A "request timed out" is when something on a server (remote or local) that is being accessed through http cannot be found. Much like when you use the ping command. If the site can't be found the request will timeout.

When a "Timeout Expired" occurs, it means that the receiving page took too long to process the request. IIS will stop the process that takes too long and through this error. It is essentially to prevent infinite loops and long requests.
atastecAuthor Commented:
Perfect, thanks!

I'm handling this by setting the debug value to true in Web.Config (http://support.microsoft.com/kb/825739).  Not a good solution, I know, but it should be ok because I'm redirecting to a custom error page in Application_Error().

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now